BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2009
CVE-2009-3555High confidence

Affected product: Channel Accessible by Non-Endpoint

Unknown · Unknown

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 87.26% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

27 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.2.14-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourcelighttpdVendor fix publishedDebian records a fixed source-package version for this release.1.4.30-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourcenginxVendor fix publishedDebian records a fixed source-package version for this release.0.7.64-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourcenssVendor fix publishedDebian records a fixed source-package version for this release.3.12.6-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.0.9.8k-6Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourcepoundVendor fix publishedDebian records a fixed source-package version for this release.2.6-6.1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian trixietrixie · sourcetomcat-nativeVendor fix publishedDebian records a fixed source-package version for this release.1.1.18-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.2.14-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourcelighttpdVendor fix publishedDebian records a fixed source-package version for this release.1.4.30-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourcenginxVendor fix publishedDebian records a fixed source-package version for this release.0.7.64-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourcenssVendor fix publishedDebian records a fixed source-package version for this release.3.12.6-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.0.9.8k-6Debian Security Tracker ↗Source updated 22 Oct 2026
Debian bookwormbookworm · sourcetomcat-nativeVendor fix publishedDebian records a fixed source-package version for this release.1.1.18-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.2.14-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcelighttpdVendor fix publishedDebian records a fixed source-package version for this release.1.4.30-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcenginxVendor fix publishedDebian records a fixed source-package version for this release.0.7.64-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcenssVendor fix publishedDebian records a fixed source-package version for this release.3.12.6-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.0.9.8k-6Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcepoundVendor fix publishedDebian records a fixed source-package version for this release.2.6-6.1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian forkyforky · sourcetomcat-nativeVendor fix publishedDebian records a fixed source-package version for this release.1.1.18-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourceapache2Vendor fix publishedDebian records a fixed source-package version for this release.2.2.14-2Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcelighttpdVendor fix publishedDebian records a fixed source-package version for this release.1.4.30-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcenginxVendor fix publishedDebian records a fixed source-package version for this release.0.7.64-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcenssVendor fix publishedDebian records a fixed source-package version for this release.3.12.6-1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourceopensslVendor fix publishedDebian records a fixed source-package version for this release.0.9.8k-6Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcepoundVendor fix publishedDebian records a fixed source-package version for this release.2.6-6.1Debian Security Tracker ↗Source updated 22 Oct 2026
Debian sidsid · sourcetomcat-nativeVendor fix publishedDebian records a fixed source-package version for this release.1.1.18-1Debian Security Tracker ↗Source updated 22 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.tomcat:tomcatECOSYSTEM: introduced 7.0.0; fixed 7.0.107.0.10OSV record ↗aggregator derived · 9 Jun 2026
Mavenorg.apache.tomcat:tomcatECOSYSTEM: introduced 6.0.0; fixed 6.0.326.0.32OSV record ↗aggregator derived · 9 Jun 2026
Mavenorg.apache.tomcat:tomcatECOSYSTEM: introduced 5.0.0; fixed 5.5.335.5.33OSV record ↗aggregator derived · 9 Jun 2026
mavenorg.apache.tomcat:tomcat>= 7.0.0, < 7.0.107.0.10GitHub advisory ↗github reviewed aggregator · 8 Jun 2026
mavenorg.apache.tomcat:tomcat>= 6.0.0, < 6.0.326.0.32GitHub advisory ↗github reviewed aggregator · 8 Jun 2026
mavenorg.apache.tomcat:tomcat>= 5.0.0, < 5.5.335.5.33GitHub advisory ↗github reviewed aggregator · 8 Jun 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-3720

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Channel Accessible by Non-Endpoint → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-300 ↗

CWE-300: Channel Accessible by Non-Endpoint. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-300Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
n/a: n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
Official vendor articles2 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 9 Nov 2009 · Last source change 27 May 2026, 15:38 UTC · CWE-300 · Channel Accessible by Non-Endpoint

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-13
European sourceENISA EUVD · EUVD-2022-3720
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2022-3720 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2022-3720"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: securityfocus.com/36935; added remediation: securityfocus.com/36935; removed remediation: docs.microsoft.com/ms10-049; removed vendor advisory: cisco.com/products_security_advisory09186a0080b01d1d.shtml; 81 further removals.
    Before
    patch: docs.microsoft.com/ms10-049 · remediation: docs.microsoft.com/ms10-049 · vendor advisory: cisco.com/products_security_advisory09186a0080b01d1d.shtml · 81 more references
    After
    patch: docs.microsoft.com/ms10-049 · patch: securityfocus.com/36935 · remediation: securityfocus.com/36935
    securityfocus.com ↗
  3. Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
    Before
    Public exploit reference
    After
    Public exploit reference
    securityfocus.com ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-3720↗CISA Vulnrichment SSVC evidence↗Public exploit reference↗Patch or update reference↗CVE authority or vendor reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2009-3555 · cve.blacktree.nl