A new 𝗰𝗿𝗶𝘁𝗶𝗰𝗮𝗹 𝘃𝘂𝗹𝗻𝗲𝗿𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗷𝘂𝘀𝘁 𝗱𝗿𝗼𝗽𝗽𝗲𝗱 — and this one affects more systems than you might expect.
Oracle has confirmed CVE-2025-61882, a 𝘇𝗲𝗿𝗼-𝗱𝗮𝘆 in Oracle E-Business Suite (EBS) actively exploited by the CL0P group in data theft and extortion campaigns. The issue lies in the Concurrent Processing / BI Publisher Integration component and enables unauthenticated remote code execution over HTTP.
What caught my eye is that the 𝗲𝘅𝗽𝗹𝗼𝗶𝘁 𝗿𝗲𝗾𝘂𝗶𝗿𝗲𝘀 𝗻𝗼 𝗰𝗿𝗲𝗱𝗲𝗻𝘁𝗶𝗮𝗹𝘀 𝗮𝘁 𝗮𝗹𝗹 — it can be 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝗲𝗱 𝗿𝗲𝗺𝗼𝘁𝗲𝗹𝘆, and the proof-of-concept code is already circulating publicly. That combination usually 𝗹𝗲𝗮𝗱𝘀 𝘁𝗼 𝗿𝗮𝗽𝗶𝗱 𝗺𝗮𝘀𝘀 𝘀𝗰𝗮𝗻𝗻𝗶𝗻𝗴, especially across 𝗲𝘅𝗽𝗼𝘀𝗲𝗱 𝗲𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝘀𝗲𝗿𝘃𝗲𝗿𝘀.
If you manage 𝗢𝗿𝗮𝗰𝗹𝗲 𝗘𝗕𝗦 12.2.3 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 12.2.14, this should be a 𝘁𝗼𝗽 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝘆 today. Oracle has released an 𝗲𝗺𝗲𝗿𝗴𝗲𝗻𝗰𝘆 𝗽𝗮𝘁𝗰𝗵, but it depends on having the October 2023 Critical Patch Update installed first — so double-check your baseline before applying it. There’s no complete workaround beyond restricting or disabling external HTTP(S) access.
When reviewing exposure, I found it particularly concerning that many organizations still expose EBS interfaces directly to the internet, often for integration purposes. In this case, that configuration could 𝗮𝗹𝗹𝗼𝘄 𝗮𝘁𝘁𝗮𝗰𝗸𝗲𝗿𝘀 𝗳𝘂𝗹𝗹 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 𝗼𝗳 𝘁𝗵𝗲 𝘀𝗲𝗿𝘃𝗲𝗿, including access to 𝘀𝗲𝗻𝘀𝗶𝘁𝗶𝘃𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗱𝗮𝘁𝗮.
💡 𝗗𝗲𝘃𝗦𝗲𝗰𝗢𝗽𝘀 𝗽𝗲𝗿𝘀𝗽𝗲𝗰𝘁𝗶𝘃𝗲
This is a good reminder of why vulnerability management can’t live in isolation. Integrating CVE feeds and Oracle patch advisories directly into CI/CD or IaC pipelines helps ensure environments are continuously validated against known risks. Automating dependency checks, infrastructure scans, and change validations can 𝗿𝗲𝗱𝘂𝗰𝗲 𝘁𝗵𝗲 𝗴𝗮𝗽 𝗯𝗲𝘁𝘄𝗲𝗲𝗻 𝗱𝗶𝘀𝗰𝗹𝗼𝘀𝘂𝗿𝗲 𝗮𝗻𝗱 𝗿𝗲𝗺𝗲𝗱𝗶𝗮𝘁𝗶𝗼𝗻 — especially for legacy systems like EBS that are often maintained manually.
If you haven’t patched yet, take these steps right away:
– Apply Oracle’s patch for CVE-2025-61882 (and the 2023 prerequisite).
– Block or limit HTTP(S) traffic to EBS endpoints.
– Hunt for IOCs in logs or EDR tools using Oracle’s published indicators.
If you’re concerned that this might affect your environment and want to understand how to verify exposure or apply the patch correctly, feel free to comment or write me — I’ll be glad to share more details and useful references.
#DevSecOps #VulnerabilityManagement #Oracle #Vulnerability
https://via.socxo.net/8EGLcaujGhyfk