Security readout for executives and security teams
This is an old IBM DB2 local file-permission flaw. The STMM log file was writable by all local users, which could let someone with host access disrupt database operation or cause unspecified impact. Exposure is most likely on legacy DB2 9.1, 9.5, or 9.7 installations below the named fix packs, especially shared Unix/Linux hosts with non-administrative local users. Prioritize remediation where affected DB2 versions support important business systems or shared host access. This is not shown as actively exploited, but database availability impact warrants cleanup. Mitigation focus: Upgrade DB2 9.1 to FP8 or later, if still in use.; Upgrade DB2 9.5 to FP5 or later, if still in use.; Upgrade DB2 9.7 to FP1 or later, if still in use..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2009-4334 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
