Apache fixed a critical SQL Injection in Apache Traffic Control

CVE-2020-17530 is a critical (CVSS 9.8) expression-language injection flaw (CWE-917) in Apache Struts 2, in which the framework forces evaluation of OGNL expressions contained in raw, attacker-supplied user input placed into certain tag attributes. An attacker triggers it by sending crafted input (for example OGNL expressions such as %{...}) that an application passes unsanitized into a tag attribute, causing Struts to evaluate the payload as code; the network attack vector requires no authentication or user interaction. Successful exploitation yields remote code execution in the context of the hosting application server, with high impact on confidentiality, integrity, and availability. All Apache Struts 2 releases from 2.0.0 through 2.5.25 are affected, and multiple Oracle products that bundle Struts - Business Intelligence, Communications Diameter Intelligence Hub, Communications Policy Management, Communications Pricing Design Center, Financial Services Data Integration Hub, Hospitality OPERA 5, and MySQL Enterprise Monitor - are also impacted. Exploitation is confirmed: CISA added the flaw to the Known Exploited Vulnerabilities catalog on 2021-11-03 (ransomware use unknown), and EPSS assigns a 95.9% probability of exploitation within 30 days (100th percentile), although no public proof-of-concept is cataloged in this data.

Do: Upgrade Apache Struts to 2.5.26 or later (or the corresponding legacy-branch fix, 2.3.68) per vendor instructions, and apply the relevant Oracle Critical Patch Updates for the bundled products listed above. Audit custom Struts applications for places where raw user input flows into tag attributes, since exposure depends on application usage, and review internet-facing Struts servers for indicators of OGNL injection exploitation. Because the flaw is on the CISA KEV list, apply the required vendor updates within the mandated remediation timeframe.

CVE-2024-45387 is an SQL injection flaw in Traffic Ops, the API component of the Apache Traffic Control CDN management platform, affecting version 8.0.0 per the Apache advisory. It is triggered when a user who already holds one of the "admin", "federation", "operations", "portal", or "steering" roles sends a specially crafted PUT request to the Traffic Ops API. Successful injection lets the attacker execute arbitrary SQL against the Traffic Ops database, allowing them to read, modify, or corrupt stored data, consistent with the high confidentiality, integrity, and availability ratings in the 8.8 CVSS score. Any operator running an affected Traffic Ops deployment is exposed, though exploitation requires an authenticated privileged account. No public proof-of-concept or confirmed in-the-wild exploitation is known yet, but EPSS places this flaw in the 99th percentile with roughly a 41.5% probability of exploitation within 30 days, so patching is urgent.

Do: Upgrade Traffic Ops to Apache Traffic Control 8.0.2 or later as recommended by the advisory. In the meantime, restrict API access to trusted networks and review accounts holding the admin, federation, operations, portal, and steering roles, since any of them can trigger the injection via crafted PUT requests. Check Traffic Ops and database logs for unexpected or anomalous SQL from API activity, and watch for public exploits given the elevated EPSS score.