NoSQL Is Not NoVulnerable
summary
NoSQL systems often ship without fine-grained controls and get widely scanned and abused: honeypots see thousands of Elasticsearch/MongoDB probes per day and researchers find ~100,000 exposed memcached instances. Older Elasticsearch enables Elasticsearch RCE via scripting; MongoDB and Elasticsearch accept JSON queries so attackers use JSON query injection using $ne and similar operators to bypass filters and return everything. Practical fixes: run current versions, enable auth/TLS, restrict network access or add a filtering proxy, set CORS correctly, and monitor logs.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:13Exposed Elasticsearch Servers
- 11:16Summary
- 12:31Memcache D
- 18:55Problem with Sequel Injection
- 19:39Deserializing Json
- 30:09Conclusion
related talks
54mNoSQL Shouldn’t Mean NoSecurity
05mNoSQL injections in Node.js: The case of MongoDB
38mNot all data is created equal: NoSQL
29mGraphQL Security Best Practices and Hardening
47mEsoteric Web Application Vulnerabilities
23m{JS-ON: Security-OFF}: Abusing JSON-Based SQL Queries
01h 01mNoSQL: An Analysis
50mNoSQL Databases You Have to Know