VYPR
Critical severity9.8NVD Advisory· Published Aug 5, 2016· Updated May 6, 2026

CVE-2016-6139

CVE-2016-6139

Description

A remote unauthenticated attacker can read arbitrary files from SAP TREX 7.10 Revision 63 via improper access control.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A remote unauthenticated attacker can read arbitrary files from SAP TREX 7.10 Revision 63 via improper access control.

Vulnerability

CVE-2016-6139 is an improper access control vulnerability (CWE-284) in SAP TREX 7.10 – Revision 63. A specific function in the TREXNet communication protocol allows a remote unauthenticated attacker to read arbitrary files from the TREX server. The vulnerability is exploitable without authentication over the network [1][2].

Exploitation

An attacker can exploit this vulnerability by sending a crafted request to the vulnerable TREX service, which listens on a TCP port. No prior authentication or user interaction is required. The attacker only needs network access to the TREX server to trigger the file read operation [1][2].

Impact

Successful exploitation leads to disclosure of arbitrary files from the SAP TREX server. This can expose sensitive business information [1][2]. The impact is limited to confidentiality; integrity and availability are not affected as per Onapsis CVSS v3 scoring [2].

Mitigation

SAP released Security Note 2203591 to address this issue, which was made available on October 13, 2015. Administrators should apply the patch as soon as possible. No workarounds are documented in the available references [1][2].

AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1
  • SAP/Trexllm-fuzzy
    Range: =7.10 Revision 63

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

6

News mentions

0

No linked articles in our index yet.