CVE-2017-14581
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 · uneditedThe Host Control web service in SAP NetWeaver AS JAVA 7.0 through 7.5 allows remote attackers to cause a denial of service (service crash) via a crafted request, aka SAP Security Note 2389181.
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 confidenceThe Host Control web service in SAP NetWeaver AS JAVA versions 7.0 through 7.5 contains a vulnerability that allows remote, unauthenticated attackers to cause a denial of service by sending specially crafted requests that crash the service. This is a network-exploitable DoS (AV:N/AC:L) with high availability impact.
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.00, <= 7.50CVSS 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.
-
Confirm SAP NetWeaver AS JAVA is installedLocate the SAP system directory and identify the JAVA stack components. Look for SAP NetWeaver AS JAVA directories or check SAP system information via SAP transaction code SM51 or the SAP Management Console.Affected if The system is running SAP NetWeaver AS JAVA without the patch from SAP Security Note 2389181
-
Determine the NetWeaver AS JAVA versionCheck the SAP system version by running the SAP transaction code SM51, viewing the SAP kernel version via the SAP Management Console, or inspecting the SAP system information file. Compare the version number against the affected range: 7.00 through 7.50.Affected if The installed version falls within >= 7.00 and <= 7.50 and the patch is not applied
-
Verify the Host Control web service is accessibleIdentify the port configured for the Host Control web service (default HTTP port for SAP Java core). Attempt to access the Host Control endpoint via HTTP request to confirm the service is listening and responding.Affected if The Host Control web service port is open and accepting requests from the network
-
Check network exposure of the Host Control serviceReview firewall rules and network configuration to determine if the Host Control web service port is reachable from untrusted networks. Use network scanning tools to identify open ports on the system.Affected if The Host Control web service port is exposed to untrusted network segments (not behind restricted access controls)
The environment is affected if it runs unpatched SAP NetWeaver AS JAVA version 7.00-7.50 with the Host Control web service accessible over the network.
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 2389181 to patch the vulnerability in affected NetWeaver AS JAVA installations. Until the patch is applied, consider restricting network access to the Host Control web service port or implementing rate limiting as a temporary mitigation.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14581 — 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-2017-14581 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