Is CVE-2017-5372 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-5372 being exploited in the wild.

How severe is CVE-2017-5372?

High severity, with a CVSS score of 7.5, published 23 January 2017.

Which products and versions are affected?

SAP NetWeaver AS Java (SERVERCORE) 7.11, 7.20, 7.30, 7.31, 7.40, 7.50.

Is there a fix for CVE-2017-5372?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2017-5372 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2017-5372?

Check whether you run SAP NetWeaver or SAP NetWeaver AS Java (SERVERCORE) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2017-5372: SAP NetWeaver AS JAVA information disclosure in P4 SERVERCORE

CVE-2017-5372 · Severity: high · CVSS 7.5 · Published 2017-01-23

A vulnerability in SAP NetWeaver AS JAVA allows unauthorized individuals to remotely access sensitive system information. The affected component is responsible for core server operations, and an exploit could allow an attacker to view system parameters, service details, and statistics without a password. This information could be used to facilitate further, more targeted attacks against the organization's SAP infrastructure.

Technologies: SAP NetWeaver, SAP NetWeaver AS Java (SERVERCORE). Vendors: SAP.

Quick answers

Is CVE-2017-5372 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2017-5372 being exploited in the wild.
How severe is CVE-2017-5372?: High severity, with a CVSS score of 7.5, published 23 January 2017.
Which products and versions are affected?: SAP NetWeaver AS Java (SERVERCORE) 7.11, 7.20, 7.30, 7.31, 7.40, 7.50.
Is there a fix for CVE-2017-5372?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2017-5372 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2017-5372?: Check whether you run SAP NetWeaver or SAP NetWeaver AS Java (SERVERCORE) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The msp (MSPRuntimeInterface) function within the P4 SERVERCORE component of SAP AS JAVA fails to perform necessary authorization checks. A remote, unauthenticated attacker can invoke several sensitive methods—including getInformation, getParameters, getServiceInfo, getStatistic, and getClientStatistic—via the P4 protocol. This allows for the retrieval of system IDs, configuration parameters, and runtime statistics. The vulnerability stems from a lack of access control on these specific JNDI-accessible functions. SAP has released Security Note 2331908 to address this issue.

Affected products

SAP NetWeaver AS JAVA (SERVERCORE) 7.11, 7.20, 7.30, 7.31, 7.40, 7.50

Timeline

2016-03-10: other: Vulnerability sent to vendor
2016-03-11: other: Vendor response received
2016-10-12: advisory: SAP Security Note 2331908 released
2017-01-23: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.