Business Intelligence PublisherApplication · Oracle

CVE-2019-2616

HIGH · 7.2 CVSS v3.1 Published 2019-04-23

Patch available

A vendor patch is available. No clean upgrade release — apply the published patch.

See remediation →

100/100

Remediation priority · Urgent

In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

Official description

NVD · unedited

Vulnerability in the BI Publisher (formerly XML Publisher) component of Oracle Fusion Middleware (subcomponent: BI Publisher Security). Supported versions that are affected are 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher). While the vulnerability is in BI Publisher (formerly XML Publisher), attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of BI Publisher (formerly XML Publisher) accessible data as well as unauthorized read access to a subset of BI Publisher (formerly XML Publisher) accessible data. CVSS 3.0 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).

Technical summary

dbcve analysis · high confidence

Vulnerability in Oracle BI Publisher's security subcomponent allows unauthenticated attackers with network access via HTTP to compromise the system. Successful exploitation grants unauthorized read and write (insert/delete/update) access to a subset of BI Publisher data, with potential for significant impact to additional products due to the application's integration scope.

MitigationApply Oracle Critical Patch Update for CVE-2019-2616 to affected versions (11.1.1.9.0, 12.2.1.3.0, 12.2.1.4.0). Until patched, restrict network access to BI Publisher HTTP interfaces and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Business Intelligence PublisherApplication

Affected:= 11.1.1.9.0= 12.2.1.3.0= 12.2.1.4.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Confirm Oracle BI Publisher is installed

Locate BI Publisher installation directory (common paths: $ORACLE_HOME/bipublisher, or check for 'XMLP' or 'bipublisher' in deployed applications). On Windows, check Services for 'Oracle Business Intelligence Publisher' service.

Affected if BI Publisher component is present on the system
Identify the installed BI Publisher version

Access the BI Publisher Administration page (typically at /xmlp/admin or /xmlpserver/about), or check the version file in the installation directory (often VERSION.txt or patch applied listings in OPatch).

Affected if Version matches exactly 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
Verify HTTP listener is exposed

Check if BI Publisher HTTP or HTTPS ports are listening (netstat -an | grep port or similar). Confirm the web application is accessible via browser to the /xmlp or /xmlpserver endpoints.

Affected if BI Publisher HTTP endpoints are reachable from network
Confirm no additional authentication layer is in place

Review the authentication configuration in BI Publisher security settings. Check if the Oracle BI Publisher web paths are protected by an external authentication mechanism such as Oracle Access Manager, SSO, or a reverse proxy with auth enforcement.

Affected if BI Publisher HTTP endpoints allow unauthenticated access without external authentication protection

User is affected if Oracle BI Publisher is installed, the installed version is exactly 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0, and the HTTP interface is accessible without additional authentication barriers.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Patch available Apply the vendor patch

Vendor patch www.oracle.com →

Interim mitigation

Apply Oracle Critical Patch Update for CVE-2019-2616 to affected versions (11.1.1.9.0, 12.2.1.3.0, 12.2.1.4.0). Until patched, restrict network access to BI Publisher HTTP interfaces and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Apply Oracle April 2019 Critical Patch Update (CPUAPR2019) or upgrade to the latest 12.2.1.x release

1. Review the Oracle Critical Patch Update advisory for April 2019 (CPUAPR2019) which contains the fix for CVE-2019-2616
2. Identify your current Oracle BI Publisher version from the affected list: 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
3. For version 11.1.1.9.0: Apply the April 2019 Critical Patch Update or upgrade to a later supported version within the 11g release line
4. For version 12.2.1.3.0: Apply the April 2019 Critical Patch Update or upgrade to version 12.2.1.4.0 or later
5. For version 12.2.1.4.0: Apply the April 2019 Critical Patch Update or upgrade to the latest 12.2.1.x version
6. After applying the patch/upgrade, verify the BI Publisher version matches the expected fixed version
7. Test the BI Publisher application to ensure functionality remains intact post-update

Caveat Upgrading Oracle BI Publisher may require configuration adjustments; test thoroughly in non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Business Intelligence Publisher Exploited in the wild — priority engagement

Consultation4.0 h
Implementation6.0 h
Testing8.0 h
Review / QA2.0 h

20.0 hours of engineering $3,440

Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2019-2616 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comPatch / commit
www.oracle.comPatchVendor Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-2616 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2019-2616?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-04-15

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 92.2%

Affects: Business Intelligence Publisher

Remediation

Being exploited — close it fast

Fix this in Business Intelligence Publisher 20 hrs · Moderate

Typical engagement from $3,440

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References