From d0b575159410284f6801b34b4c2e8f33f3cf993e Mon Sep 17 00:00:00 2001 From: Sanjeev Jaiswal Date: Thu, 14 Apr 2022 14:51:20 +0530 Subject: [PATCH] Added one link under Security bulletin https://infosecwriteups.com/how-i-discovered-thousands-of-open-databases-on-aws-764729aa7f32 --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 8f588c8..c01e077 100644 --- a/README.md +++ b/README.md @@ -169,6 +169,7 @@ And don't forget to **bookmark AWS Security bulletin** for new vulnerabilities n 4. [CBC padding oracle issue in AWS S3 Crypto SDK for golang](https://github.com/google/security-research/security/advisories/GHSA-f5pg-7wfw-84q9) : [CVE-2020-8911](https://nvd.nist.gov/vuln/detail/CVE-2020-8911) 5. [In-band key negotiation issue in AWS S3 Crypto SDK for golang](https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw) : [CVE-2020-8912](https://nvd.nist.gov/vuln/detail/CVE-2020-8912) 6. [CVE-2018-15869](https://nvd.nist.gov/vuln/detail/CVE-2018-15869): An Amazon Web Services (AWS) developer who does not specify the --owners flag when describing images via AWS CLI, and therefore not properly validating source software per AWS recommended security best practices, may unintentionally load an undesired and potentially malicious Amazon Machine Image (AMI) from the uncurated public community AMI catalog. +7. [How a Security Researcher found 1000s of open databases on AWS](https://infosecwriteups.com/how-i-discovered-thousands-of-open-databases-on-aws-764729aa7f32) ## AWS Security Breaches 1. [AWS Security breaches - 2017](https://www.sumologic.com/blog/aws-security-breaches-2017/)