Accidentally Secure Is Not Secure: A Case of Three Stooges Syndrome
bishopfox.com | blog | #appsec | #vulnerability-management | #sql-injection | #penetration-testing | #risk-prioritization
Summary
'Accidentally secure' isn't secure: a SQL injection capped by an 8-character field limit can become exploitable after routine code changes, so don't ignore not-yet-exploitable findings.
- Published
- Collected
--- id: 4110 title: "Accidentally Secure Is Not Secure: A Case of Three Stooges Syndrome" source_domain: bishopfox.com source_url: "https://bishopfox.com/blog/accidentally-secure-not-secure" published_at: "2020-10-20T00:00:00Z" tags: ["appsec", "vulnerability-management", "sql-injection", "penetration-testing", "risk-prioritization"] phying_url: "https://phying.com/item/4110" lang: en --- # Accidentally Secure Is Not Secure: A Case of Three Stooges Syndrome ## Summary 'Accidentally secure' isn't secure: a SQL injection capped by an 8-character field limit can become exploitable after routine code changes, so don't ignore not-yet-exploitable findings. ## Intelligence Metadata - **Sources:** bishopfox.com - **Published:** 2020-10-20T00:00:00Z - **Original:** https://bishopfox.com/blog/accidentally-secure-not-secure - **Phying News:** https://phying.com/item/4110