LiveActive security incident?Get immediate response
CVE Record

CVE-2019-2771: Vulnerability in the BI Publisher (formerly XML Publisher) component of Oracle Fusion Middleware (subcompon...

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 and 12.2.1.3.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher). Successful attacks require human interaction from a person other than the attacker and 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 creation, deletion or modification access to critical data or all BI Publisher (formerly XML Publisher) accessible data as well as unauthorized read access to a subset of BI Publisher (formerly XML Publisher) accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of BI Publisher (formerly XML Publisher). CVSS 3.0 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:L).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2019-2771 affects Oracle BI Publisher in specific Oracle Fusion Middleware versions. A low-privileged attacker with HTTP access could, with another user's interaction, compromise BI Publisher data and availability. The main business risk is unauthorized change or deletion of critical BI Publisher-accessible data. Exposure is most likely where affected BI Publisher versions are reachable over HTTP by low-privileged authenticated users. The sources do not identify other affected products by name, though Oracle notes possible impact beyond BI Publisher. Treat this as high priority for any exposed affected BI Publisher deployment because integrity impact is high and critical data could be changed or deleted. Prioritize inventory, vendor guidance review, and remediation confirmation. Mitigation focus: Confirm whether BI Publisher 11.1.1.9.0 or 12.2.1.3.0 is deployed.; Review Oracle July 2019 Critical Patch Update guidance for the applicable release.; Apply Oracle-supported fixes or upgrade guidance where Oracle marks the deployment affected..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-2771 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationBI Publisher (formerly XML Publisher)11.1.1.9.0, 12.2.1.3.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.