CVE-2014-2749
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 HANA ICM process in SAP HANA allows remote attackers to obtain the platform version, host name, instance number, and possibly other sensitive information via a malformed HTTP GET request.
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 · moderate confidenceThe vulnerability exists in SAP HANA's ICM (Internet Communication Manager) process. A remote attacker can send a malformed HTTP GET request to the ICM interface and receive sensitive system information in the response, including the SAP HANA platform version, hostname, instance number, and potentially other configuration details.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Verify ICM is running and exposedCheck if the Internet Communication Manager process is running on the SAP HANA system. Common ICM ports include 80xx or 5xxxx. Use netstat or similar tools to see if ICM ports are listening.Affected if ICM ports are open and listening on network interfaces accessible to untrusted users
-
Identify ICM port exposureReview firewall rules, SAP profile parameters (icm/HTTP_PORT), and network ACLs to determine if the ICM port is accessible from untrusted network segments.Affected if The ICM port is accessible from external or untrusted networks without proper access controls
-
Test for information disclosureSend a malformed HTTP GET request to the ICM endpoint (e.g., GET / HTTP/1.1 with intentionally malformed headers or incomplete request) and observe if the response contains system details such as SAP HANA version, hostname, or instance number.Affected if The malformed request returns sensitive system information including version, hostname, or instance number in the response headers or body
-
Review ICM configurationCheck SAP HANA profile parameters related to ICM (icm/display_version, icm/HTTP_port) and verify whether verbose error reporting is enabled that could leak system details.Affected if ICM is configured to display version information or detailed system errors to incoming requests
A user is affected if the ICM interface is network-accessible and responds to malformed HTTP requests with sensitive system information such as version, hostname, or instance number.
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 the relevant SAP security patch for CVE-2014-2749. Additionally, restrict network access to the ICM port and implement WAF rules to detect and block malformed HTTP requests targeting the ICM endpoint.
- Consultation8.0 h
- Implementation4.0 h
- Testing4.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 $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2749 — 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-2014-2749 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