CVE-2013-3319
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 GetComputerSystem method in the HostControl service in SAP Netweaver 7.03 allows remote attackers to obtain sensitive information via a crafted SOAP request to TCP port 1128.
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 GetComputerSystem method in the HostControl service of SAP Netweaver 7.03 exposes sensitive system information to remote unauthenticated attackers via crafted SOAP requests on TCP port 1128. This is an information disclosure vulnerability resulting from missing authentication on the HostControl SOAP endpoint.
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.03CVSS 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.
-
Identify installed SAP NetWeaver versionDetermine the exact version of SAP NetWeaver installed in your environment using SAP transaction SM37 or by checking the SAP system profile. Look specifically for version 7.03.Affected if Installed version is SAP NetWeaver 7.03 exactly
-
Confirm HostControl service is activeVerify whether the HostControl service is running on the SAP system. Use SAP transaction SMICM to check the ICM monitor and look for the ICF service /sap/hostctrl, or check via SAP Management Console.Affected if HostControl service is enabled and running
-
Check if port 1128 is listeningScan the system to determine if TCP port 1128 is open and listening. Use commands such as netstat -an | grep 1128, nmap, or port scanning tools to confirm the port is accessible.Affected if Port 1128 is open and accepting connections
-
Test SOAP endpoint without authenticationSend a crafted SOAP request to the HostControl endpoint on port 1128 without providing any authentication credentials. If the GetComputerSystem method returns sensitive system information, the vulnerability is present.Affected if SOAP endpoint responds to unauthenticated requests with system information
If running SAP NetWeaver 7.03 with HostControl enabled on accessible port 1128 that returns system data without authentication, the environment is affected.
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 dataRestrict network access to TCP port 1128 to trusted IPs only, or disable the HostControl service if not required, and apply any available SAP security notes for this issue.
- 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-2013-3319 — 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-2013-3319 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