LiveActive security incident?Get immediate response
CVE Record

CVE-2013-1451: Microsoft Internet Explorer 8 and 9, when the Proxy Settings configuration has the same Proxy address and P...

Microsoft Internet Explorer 8 and 9, when the Proxy Settings configuration has the same Proxy address and Port values in the HTTP and Secure rows, does not ensure that the SSL lock icon is consistent with the Address bar, which makes it easier for remote attackers to spoof web sites via a crafted HTML document that triggers many HTTPS requests to an arbitrary host, followed by an HTTPS request to a trusted host and then an HTTP request to an untrusted host, a related issue to CVE-2013-1450.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a browser trust-indicator problem in Internet Explorer 8 and 9. Under a specific proxy configuration, the SSL lock icon could disagree with the address bar, making a spoofed site appear more trustworthy to users. The sources do not provide a CVSS score, vendor patch details, or evidence of active exploitation. Exposure appears limited to environments still using Internet Explorer 8 or 9 with the proxy settings configuration described in the CVE. The provided affected-product metadata is incomplete, so validation should focus on browser inventory and proxy configuration evidence. Treat this as a legacy-browser exposure question rather than an emergency by default. If Internet Explorer 8 or 9 remains in business workflows, prioritize removal or compensating controls because the issue undermines a visible user trust signal. Mitigation focus: Check Microsoft guidance for CVE-2013-1451 and related browser updates.; Inventory and remove remaining Internet Explorer 8 or 9 dependencies.; Review proxy settings for identical HTTP and Secure proxy address and port values..

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-1451 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
1Source 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.