CVE-2013-0518

UnknownEPSS 0.80%

Last modified

CVE-2013-0518 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.80% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.80%

51.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
IbmSterling Secure Proxy3.2.0.0
IbmSterling Secure Proxy3.3.0.1
IbmSterling Secure Proxy3.4.0.0
IbmSterling Secure Proxy3.4.1.0
IbmSterling Secure Proxy3.4.1.2
IbmSterling Secure Proxy3.4.1.5
IbmSterling Secure Proxy3.4.1.6

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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 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.
How severe is CVE-2013-0518?
Severity scoring for CVE-2013-0518 is pending analysis. The EPSS model estimates a 0.80% probability of exploitation in the next 30 days.
How do I fix CVE-2013-0518?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-0518?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST