CVE-2016-9562
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSAP NetWeaver AS JAVA 7.4 allows remote attackers to cause a Denial of Service (null pointer exception and icman outage) via an HTTPS request to the sap.com~P4TunnelingApp!web/myServlet URI, aka SAP Security Note 2313835.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn SAP NetWeaver AS JAVA 7.4, a remote attacker can send a crafted HTTPS request to the sap.com~P4TunnelingApp!web/myServlet URI, triggering a null pointer exception that causes the icman service to crash, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.40CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS Java versionUse SAP administration tools (such as SAP MMC, SAP Management Console, or version query commands) to determine the installed version of SAP NetWeaver Application Server Java. Common methods include checking via SAP's software provisioning manager or querying the system kernel version.Affected if The installed version is exactly 7.40 (specifically reported as version = 7.40)
-
Verify P4TunnelingApp component deploymentCheck if the P4TunnelingApp application component is deployed on the SAP NetWeaver AS Java system. This can typically be verified through SAP's deployment management tools or by inspecting the deployed applications list in the SAP administration console.Affected if The P4TunnelingApp component (identified as sap.com~P4TunnelingApp) is present in the deployed applications list
-
Confirm vulnerable servlet endpoint existsInspect whether the servlet at the URI path sap.com~P4TunnelingApp!web/myServlet is accessible or registered in the web application configuration. This endpoint is the specific path used to trigger the null pointer exception.Affected if The servlet endpoint at sap.com~P4TunnelingApp!web/myServlet exists and is reachable via HTTPS requests
-
Verify icman service statusCheck the status of the icman (ICM - Internet Communication Manager) service on the SAP NetWeaver system. The vulnerability causes this service to crash when triggered. This can be verified through SAP management tools or system service monitoring.Affected if The icman service is running and accessible, as the flaw causes this specific service to crash upon exploitation
A system is affected if it runs SAP NetWeaver AS Java version 7.40 with the P4TunnelingApp component deployed and the vulnerable servlet endpoint accessible, making the icman service susceptible to crash via crafted HTTPS requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply SAP Security Note 2313835 which provides the patch to fix the null pointer exception in the P4TunnelingApp component.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-9562 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data