CVE-2009-3555: The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information...
The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
Security readout for executives and security teams
This is an old but serious TLS/SSL design flaw. A network attacker positioned between a user and server could splice unauthenticated data into a protected session during renegotiation. Business risk is highest where legacy HTTPS, VPN, mail, or appliance services still use affected TLS/SSL stacks or have unsafe renegotiation enabled. Exposure is most likely in legacy systems, embedded appliances, old middleware, or unsupported operating systems using SSLv3, early TLS, or outdated TLS libraries listed in the CVE. Modern patched TLS stacks are less likely to be exposed, but estates with old network devices or long-lived servers need confirmation. Prioritize discovery and remediation on legacy internet-facing systems and network appliances. This CVE is critical by score, but urgency depends on whether unsafe renegotiation remains present in the environment. Lack of KEV evidence lowers active-incident urgency but not the need to eliminate legacy exposure. Mitigation focus: Inventory internet-facing and internal TLS services, including appliances and legacy middleware.; Apply relevant vendor security updates for affected TLS libraries and products.; Disable unsafe SSL/TLS renegotiation where vendor guidance supports it..
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.
cwe · low confidence lookup
CWE-300: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-300 · source CWE mapping
Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.