LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0520: IBM 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...

IBM 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 allows remote authenticated users to obtain sensitive Java stack-trace information by providing invalid input data.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-0520 is an information disclosure issue in older IBM Sterling Secure Proxy releases. An authenticated remote user could submit invalid input and receive sensitive Java stack-trace details. This is not described as remote code execution, but leaked internals can help attackers understand the environment and plan follow-on activity. Exposure is most likely in organizations still running legacy IBM Sterling Secure Proxy 3.2.0, 3.3.01, 3.4.0, or 3.4.1 deployments below the fixed interim-fix levels. The source bundle does not identify affected operating systems, deployment modes, or default exposure conditions. Prioritize remediation where Sterling Secure Proxy is internet-reachable or used by external partners. The issue is lower urgency than unauthenticated compromise, but it can leak operational details that reduce attacker effort. Unsupported or forgotten legacy deployments should be handled promptly. Mitigation focus: Identify all IBM Sterling Secure Proxy deployments and recorded version levels.; Apply IBM's referenced interim fixes or later supported maintenance where applicable.; Review IBM advisory guidance before changing production configurations..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-0520 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.