LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10043: Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: BI Publisher Security).

Vulnerability in the BI Publisher component of Oracle Fusion Middleware (subcomponent: BI Publisher Security). Supported versions that are affected are 11.1.1.7.0 and 11.1.1.9.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in BI Publisher, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all BI Publisher accessible data as well as unauthorized update, insert or delete access to some of BI Publisher accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Oracle BI Publisher flaw can let an unauthenticated network attacker compromise BI Publisher if they can get another person to interact with the attack. The stated impact is serious: access to critical BI Publisher data, potentially all BI Publisher-accessible data, and limited unauthorized data changes. Exposure is likely where Oracle BI Publisher 11.1.1.7.0 or 11.1.1.9.0 is reachable over HTTP, including internal portals and externally exposed deployments. Environments without those versions are not indicated as affected by the provided sources. Treat this as high priority for any affected BI Publisher deployment because the vulnerability can expose critical reporting data and permit some unauthorized data modification. Urgency is highest for HTTP-accessible systems and environments storing sensitive operational, financial, or customer data. Mitigation focus: Check Oracle July 2017 CPU guidance for vendor-directed remediation.; Apply the relevant Oracle security update or supported upgrade path.; Restrict BI Publisher HTTP access to trusted networks until remediated..

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-2017-10043 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.7.0, 11.1.1.9.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.