Security readout for executives and security teams
This flaw is in ApacheBench, the Apache benchmarking client, not the web server request path itself. A malicious web server could send an overly long response that crashes ApacheBench and might execute code on the machine running the benchmark. Exposure is mainly legacy systems or test automation still using old ApacheBench builds. Likely exposure is limited to hosts with old ApacheBench binaries, commonly from legacy Apache or apache-utils packages. Risk is highest when administrators, monitoring jobs, CI tests, or scripts benchmark untrusted, compromised, or externally controlled web servers. Treat this as a legacy hygiene issue unless old benchmarking tools are still used. It is not KEV-listed in the provided bundle, but possible code execution on admin or CI systems makes cleanup worthwhile during vulnerability backlog reduction. Mitigation focus: Upgrade ApacheBench through Apache 1.3.27, Apache 2.0.43, or vendor-patched packages.; Remove ApacheBench from systems where benchmarking is not operationally required.; Avoid running legacy ApacheBench against untrusted or externally controlled web servers..
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2002-0843 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
- [httpd-cvs] 20210330 svn commit: r1073139 [1/13] - in /websites/staging/httpd/trunk/content: ./ security/json/CVE reference · mailing-list, x_refsource_MLIST
- [httpd-cvs] 20210330 svn commit: r1073140 [1/4] - in /websites/staging/httpd/trunk/content: ./ security/cvejsontohtml.py security/vulnerabilities_13.html security/vulnerabilities_20.html security/vulnerabilities_22.html security/vulnerabilities_24.htmlCVE reference · mailing-list, x_refsource_MLIST
- [httpd-cvs] 20210330 svn commit: r1073149 [2/13] - in /websites/staging/httpd/trunk/content: ./ security/ security/json/CVE reference · mailing-list, x_refsource_MLIST
- [httpd-cvs] 20210330 svn commit: r1073149 [1/13] - in /websites/staging/httpd/trunk/content: ./ security/ security/json/CVE reference · mailing-list, x_refsource_MLIST
- [httpd-cvs] 20210603 svn commit: r1075360 [1/3] - in /websites/staging/httpd/trunk/content: ./ security/json/CVE-2021-31618.json security/vulnerabilities_13.html security/vulnerabilities_20.html security/vulnerabilities_22.html security/vulnerabilities_24.htmlCVE reference · mailing-list, x_refsource_MLIST
- [httpd-cvs] 20210606 svn commit: r1075470 [1/4] - in /websites/staging/httpd/trunk/content: ./ security/json/CVE-2020-13938.json security/vulnerabilities_13.html security/vulnerabilities_20.html security/vulnerabilities_22.html security/vulnerabilities_24.htmlCVE reference · mailing-list, x_refsource_MLIST
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.