CVE-2013-2367
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 · uneditedMultiple unspecified vulnerabilities in HP SiteScope 11.20 and 11.21, when SOAP is used, allow remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1678.
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 confidenceHP SiteScope versions 11.20 and 11.21 contain multiple critical vulnerabilities in their SOAP interface that allow remote, unauthenticated attackers to execute arbitrary code on the affected system. The vulnerabilities are exploited through the SOAP web service endpoint without requiring any authentication credentials.
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= 11.20= 11.21CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 if HP SiteScope is installedCheck for HP SiteScope installation directory (typically under C:\Program Files\HP\SiteScope on Windows or /opt/HP/SiteScope on Linux). Also check for SiteScope services or processes running on the system.Affected if HP SiteScope software is found on the system
-
Determine the installed versionAccess the SiteScope administration interface and look for the version number typically displayed on the main page or in Help > About. Alternatively, check version files in the installation directory or logs for strings like 'SiteScope 11.20' or 'SiteScope 11.21'.Affected if The installed version is exactly 11.20 or 11.21
-
Verify SOAP interface accessibilityCheck if the SOAP web service endpoint is accessible by attempting to access the SiteScope SOAP URL (typically at /SiteScope/soap) from the network. Look for SOAP service configuration in SiteScope settings or examine the services.xml file in the configuration directory.Affected if The SOAP interface is enabled and reachable over the network
-
Confirm the system is reachable over the networkVerify that the SiteScope server is exposed on the network and the SOAP port (default 8080 or 8443) is open to untrusted networks. Check firewall rules and network ACLs.Affected if The SiteScope SOAP endpoint is accessible from untrusted networks without authentication
The system is affected if HP SiteScope version 11.20 or 11.21 is installed and the SOAP interface is accessible over the network to unauthenticated users.
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 dataUpgrade HP SiteScope to a patched version (11.23 or later) that addresses these vulnerabilities. If immediate patching is not feasible, consider disabling the SOAP interface or placing it behind a properly authenticated network boundary.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2367 — 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-2367 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