Unauthenticated SQL Injection Could Expose 45 Databases and 240+ S3 Buckets

Summary
CloudSEK says it found an unauthenticated SQL injection flaw in a recruitment provider’s API that could expose 45 databases, 9,000+ tables, 240+ S3 buckets and cloud infrastructure.
Key points
- CloudSEK’s BeVigil API Scanner identified a publicly accessible, unauthenticated endpoint vulnerable to SQL injection.
- The flaw could allow access to 45 databases, more than 9,000 tables and over 240 S3 buckets.
- CloudSEK says the vulnerability could enable remote command execution and expose IAM credentials, potentially allowing further access within the cloud environment.
- The article describes possible exposure of customer, payroll, financial and internal business records; it does not establish that attackers exploited the flaw or that a breach occurred.
- Recommended mitigations include requiring API authentication and authorization, using parameterized queries, limiting database privileges, rotating exposed credentials, auditing systems and deploying a web application firewall.
Article Details
- Vulnerability Types
- SQL injection
- Severity
- Critical
- Exploitation Status
- unknown
- Exploit Availability
- unknown
- Patch Status
- unknown
- Workarounds
- Implement authentication and authorization for API endpoints.
- Use parameterized queries.
- Restrict database access to necessary privileges.
- Rotate exposed IAM keys, API tokens, and database credentials.
- Use web application firewalls to block malicious SQL injection attempts.
Products
AWSAttackers could execute arbitrary system commands, potentially leading to a full compromise of the AWS cloud environment. Furthermore, the exposure of IAM credentials could have enabled lateral movement within theBeVigilOne such critical flaw was recently uncovered by CloudSEK’s BeVigil, where an unauthenticated API endpoint on a major recruitment service provider’s web application was found vulnerable to SQL Injection, potentiallyS3Access 240+ S3 Buckets containing sensitive data.
