CVE-2013-0519
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 · uneditedIBM Sterling Secure Proxy 3.2.0 and 3.3.01 before 3.3.01.23 Interim Fix 1, 3.4.0 before 3.4.0.6 Interim Fix 1, and 3.4.1 before 3.4.1.7 provides web-server version data in (1) an unspecified page title and (2) an unspecified HTTP header field, which allows remote attackers to obtain potentially sensitive information by reading a version string.
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 confidenceIBM Sterling Secure Proxy versions 3.2.0, 3.3.01 before IF1, 3.4.0 before IF6, and 3.4.1 before IF7 expose web server version information through unspecified page titles and HTTP response headers, allowing remote attackers to gather system reconnaissance data.
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= 3.2.0.0= 3.3.0.1= 3.4.0.0= 3.4.1.0= 3.4.1.2= 3.4.1.5= 3.4.1.6CVSS 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 IBM Sterling Secure Proxy versionLocate the version information in the product installation directory, typically in a version file, about dialog, or by logging into the administrative console and checking the system information or about sectionAffected if The installed version matches one of the following: 3.2.0.0, 3.3.0.1, 3.4.0.0, 3.4.1.0, 3.4.1.2, 3.4.1.5, or 3.4.1.6
-
Probe HTTP response headers for version disclosureUse a tool such as curl -I, browser developer tools, or a network packet capture to send an HTTP request to the Sterling Secure Proxy web interface and examine the Server header and any other headers for version stringsAffected if The HTTP response headers contain version numbers such as 3.2.0, 3.3.0.1, 3.4.0, or 3.4.1.x that indicate the product and version
-
Inspect web page titles for version informationAccess the login or administrative pages of the Sterling Secure Proxy web interface using a browser and view the page source or hover over the page tab to observe the title stringAffected if The page title includes version numbers or build identifiers that reveal the specific product version
-
Compare against known affected version rangesDocument the exact version found from the above checks and compare it to the affected versions: 3.2.0.0, 3.3.0.1, 3.4.0.0, 3.4.1.0, 3.4.1.2, 3.4.1.5, and 3.4.1.6Affected if The detected version exactly matches any version in the affected list
If the installed version matches any of the affected versions (3.2.0.0, 3.3.0.1, 3.4.0.0, 3.4.1.0, 3.4.1.2, 3.4.1.5, or 3.4.1.6) and the web interface exposes version information in HTTP headers or page titles, the environment is vulnerable to CVE-2013-0519.
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 appropriate Interim Fix (3.3.01.23 IF1, 3.4.0.6 IF1, or 3.4.1.7) to remediate, or configure the embedded web server to suppress version disclosure in HTTP headers and page titles.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0519 — 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-0519 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