← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2019-2616 exploited? Yes: in CISA KEV since 25 Mar 2022

Gociux · Oracle BI Publisher (Formerly XML Publisher) · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2019-2616, Oracle BI Publisher Unauthorized Access Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 25 Mar 2022, 1067 days after it was published. It affects Oracle BI Publisher (Formerly XML Publisher). If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 25 Mar 2022
ransomwareNot knownno confirmed use
EPSStop 1%among the most likely CVEs to be exploited
severity7.2CVSS 3.1 · high
US federal due15 Apr 2022BOD 22-01 deadline

What it is

Oracle BI Publisher, formerly XML Publisher, contains an unspecified vulnerability that allows for various unauthorized actions. Open-source reporting attributes this vulnerability to allowing for authentication bypass.

VendorOracle (46 exploited CVEs in KEV)
ProductBI Publisher (Formerly XML Publisher)
VulnerabilityOracle BI Publisher Unauthorized Access Vulnerability
Weaknessnot specified
Published23 Apr 2019
Added to KEV25 Mar 2022
Reported by (CNA)oracle

What to do

  1. Check whether you run it. Look for BI Publisher (Formerly XML Publisher) in your asset inventory, including appliances and cloud images. Stack check lists every exploited Oracle CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 23 Apr 2019.
  4. Get told next time. Email alerts when CISA adds a CVE for Oracle.

References

Questions

Is CVE-2019-2616 being exploited?

Yes. CISA added CVE-2019-2616 to the Known Exploited Vulnerabilities catalog on 25 Mar 2022, which means there is reliable evidence of exploitation in the wild.

Is CVE-2019-2616 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2019-2616?

Apply updates per vendor instructions. Check Oracle's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected BI Publisher (Formerly XML Publisher) and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in March 2022 · Oracle scorecard · act-now radar.

Running Oracle in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →