LiveActive security incident?Get immediate response
CVE Record

CVE-2006-0732: Directory traversal vulnerability in SAP Business Connector (BC) 4.6 and 4.7 allows remote attackers to rea...

Directory traversal vulnerability in SAP Business Connector (BC) 4.6 and 4.7 allows remote attackers to read or delete arbitrary files via the fullName parameter to (1) sapbc/SAP/chopSAPLog.dsp or (2) invoke/sap.monitor.rfcTrace/deleteSingle. Details will be updated after the grace period has ended. NOTE: SAP Business Connector is an OEM version of webMethods Integration Server. webMethods states that this issue can only occur when the product is installed as root/admin, and if the attacker has access to a general purpose port; however, both are discouraged in the documentation. In addition, the attacker must already have acquired administrative privileges through other means.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2006-0732 affects SAP Business Connector 4.6 and 4.7. It can allow arbitrary file read or deletion, but cited notes say the scenario requires unsafe deployment conditions and prior administrative privileges. Treat exposed legacy SAP BC systems as a cleanup priority, not evidence of active compromise. Exposure is most likely in legacy SAP Business Connector 4.6 or 4.7 deployments, especially internet- or broadly network-reachable instances installed with elevated OS privileges. Evidence is insufficient for other affected products or versions. Prioritize discovery and containment of old SAP BC systems. Business urgency rises sharply if the service is externally reachable or runs with elevated OS privileges. No source confirms active exploitation, so urgency should be risk-based rather than incident-level. Mitigation focus: Inventory SAP Business Connector 4.6 and 4.7 instances.; Check SAP, webMethods, and advisory guidance for supported fixes.; Avoid running SAP BC as root or administrator..

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2006-0732 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
n/an/an/aListed
Weakness

CWE details

No CWE listed

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