LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0518: 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 does not refuse to be rendered in different-origin frames, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web site.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue lets an attacker place IBM Sterling Secure Proxy pages inside a malicious web page frame, increasing the chance a logged-in user can be tricked into clicking unintended actions. The sources describe a clickjacking risk, not direct server takeover. Business urgency depends on whether affected Sterling Secure Proxy versions remain in use and who can reach their web interface. Exposure is likely limited to organizations still running the named IBM Sterling Secure Proxy versions. Risk is higher where authenticated users can reach the affected web interface from browsers that can also visit attacker-controlled pages. The supplied bundle does not identify affected deployment modes beyond the product and versions. Prioritize confirmation if Sterling Secure Proxy is still present, especially in regulated file-transfer environments. This is not evidenced as actively exploited, but legacy product exposure and authenticated-user clickjacking can still create operational risk. Patch or retire affected versions during the next controlled maintenance window unless the interface is broadly reachable. Mitigation focus: Upgrade to the IBM fixed levels named in the advisory where applicable.; Review IBM vendor guidance for any current replacement advisories or supported upgrade paths.; Restrict access to Sterling Secure Proxy administrative interfaces to trusted networks and users..

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-0518 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.