LiveActive security incident?Get immediate response
CVE Record

CVE-2009-0580: Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when FORM authenticatio...

Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18, when FORM authentication is used, allows remote attackers to enumerate valid usernames via requests to /j_security_check with malformed URL encoding of passwords, related to improper error checking in the (1) MemoryRealm, (2) DataSourceRealm, and (3) JDBCRealm authentication realms, as demonstrated by a % (percent) value for the j_password parameter.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2009-0580 is a user-enumeration issue in old Apache Tomcat versions using FORM authentication. An attacker could distinguish valid usernames by causing malformed password input to be handled differently. This does not directly give access, but it can improve password-guessing, phishing, or account-targeting campaigns against legacy Tomcat applications. Exposure is most likely in legacy Java web applications still running the listed Tomcat branches with FORM authentication and one of the named realms. Modern, supported Tomcat deployments are less likely affected, but embedded or vendor-bundled Tomcat copies should be checked. Treat this as a legacy exposure cleanup item with moderate urgency. It is unlikely to be a standalone breach path, but it can materially help attackers target accounts if old Tomcat authentication pages remain exposed. Mitigation focus: Upgrade Tomcat or vendor packages outside the listed vulnerable ranges using Apache or OS vendor guidance.; Inventory embedded Tomcat copies in commercial products and appliances, not only standalone servers.; Avoid exposing legacy FORM authentication endpoints directly to the internet where possible..

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-2009-0580 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
8Source 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.