Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 12.38% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2009
CVE-2009-1191High confidence
Affected product: security vulnerability
Unknown · Unknown
5.0MediumCVSS 2.0
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-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.
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 release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | apache2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.2.11-4 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian bookwormbookworm · source | apache2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.2.11-4 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian forkyforky · source | apache2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.2.11-4 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
| Debian sidsid · source | apache2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.2.11-4 | Debian Security Tracker ↗Source updated 22 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2009-1191 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2009-1191
The vendor recommends these product versions as the target state.
- apache2-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-devel-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-doc-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-prefork-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-utils-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-worker-2.4.33-3.15.1 as component of SUSE Enterprise Storage 6
- apache2-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- apache2-devel-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- apache2-doc-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- apache2-example-pages-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- apache2-prefork-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- apache2-utils-2.2.12-1.51.52.1 as component of SUSE Linux Enterprise Desktop 11 SP4
- Summary
- mod_proxy_ajp.c in the mod_proxy_ajp module in the Apache HTTP Server 2.2.11 allows remote attackers to obtain sensitive response data, intended for a client that sent an earlier POST request with no request body, via an HTTP request.
- Remediation
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
mod_proxy_ajp.c in the mod_proxy_ajp module in the Apache HTTP Server 2.2.11 allows remote attackers to obtain sensitive response data, intended for a client that sent an earlier POST request with no request body, via an HTTP request.
What
mod_proxy_ajp.c in the mod_proxy_ajp module in the Apache HTTP Server 2.2.11 allows remote attackers to obtain sensitive response data, intended for a client that sent an earlier POST request with no request body, via an HTTP request.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
mod_proxy_ajp.c in the mod_proxy_ajp module in the Apache HTTP Server 2.2.11 allows remote attackers to obtain sensitive response data, intended for a client that sent an earlier POST request with no request body, via an HTTP request.
Why
The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.
How
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. 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 No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Unspecified
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Not stated in the selected CVSS metric
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not stated in the selected CVSS metric
- Weakness
?
CWE means Common Weakness Enumeration. - CWE not yet assigned
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. AV:N/AC:L/Au:N/C:P/I:N/A:N- 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.
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
- Action
- To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 23 Apr 2009 · Last source change 7 Aug 2024, 05:04 UTC · CWE not yet assigned
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-13
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2009-1190
Product sourceUnavailable
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment
Missing structured fields: CWE classification, affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2009-1190 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2009-1190"}
- Vendor guidanceAuthoritative vendor guidance changed: added patch: apache.org/PR46949.diff; added patch: securityfocus.com/34663; removed vendor advisory: lists.apple.com/msg00000.html; removed vendor advisory: mandriva.com/advisories?name=MDVSA-2009:102; 3 further additions; 3 further removals.securityfocus.com ↗
- Before
- vendor advisory: lists.apple.com/msg00000.html · vendor advisory: mandriva.com/advisories?name=MDVSA-2009:102 · vendor advisory: mandriva.com/advisories?name=MDVSA-2013:150 · 2 more references
- After
- patch: apache.org/PR46949.diff · patch: securityfocus.com/34663 · patch: svn.apache.org/CHANGES?r1=766938&r2=767089 · 2 more references
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- n/a: n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 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.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.securityfocus.com ↗
- Before
- Awaiting fix
- After
- Patch available
- SeveritySeverity changed from Unknown to Medium.NIST NVD ↗
- Before
- Unknown
- After
- Medium
- CVSS scoreCVSS score changed from not recorded to 5.0 (CVSS 2.0 · NIST NVD · AV:N/AC:L/Au:N/C:P/I:N/A:N).NIST NVD ↗
- Before
- not recorded
- After
- 5.0 (CVSS 2.0 · NIST NVD · AV:N/AC:L/Au:N/C:P/I:N/A:N)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
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.