What is CVE-2021-42013?A critical-severity flaw criminals are using now.
CVE-2021-42013 is a critical-severity flaw (CVSS 9.8) in HTTP Server from Apache, published on 7 October 2021. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at over 99%. If you run an affected version, patch it first.
Published 7 October 2021. Record last updated 27 October 2025. We keep this page's data up to date.
What is CVE-2021-42013? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It was found that the fix for CVE-2021-41773 in Apache HTTP Server 2.4.50 was insufficient. An attacker could use a path traversal attack to map URLs to files outside the directories configured by Alias-like directives. If files outside of these directories are not protected by the usual default configuration "require all denied", these requests can succeed. If CGI scripts are also enabled for these aliased pathes, this could allow for remote code execution. This issue only affects Apache 2.4.49 and Apache 2.4.50 and not earlier versions.
What kind of flaw is it?
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2021-42013 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.
Timeline
- Published
- Record last updated
CVE-2021-42013 scores 90. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2021-42013 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2021-42013? 6 products.
The published record lists 6 products from 4 vendors. Versions are shown as published: "before 9.2.6.0" means every version up to, but not including, 9.2.6.0. If you run one of these, check your version, then go to the fix below.
- Application
HTTP Server
by Apache
Affected versions2.4.492.4.50 - Application
Instantis Enterprisetrack
by Oracle
Affected versions17.117.217.3 - Operating system
Fedora
Affected versions3435 - Application
Cloud Backup
by Netapp
Affected versionsversion not specified - Application
Jd Edwards Enterpriseone Tools
by Oracle
Affected versionsbefore 9.2.6.0 - Application
Secure Backup
by Oracle
Affected versionsbefore 18.1.0.1.0
How do I fix CVE-2021-42013? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
References
30 links- R17a4c6ce9aff662efd9459e9d1850ab4a611cb23392fc68264c72cb3@<cvs.httpd.apache.org> (opens in a new tab)apache.org
- Cpuapr2022 (opens in a new tab)oracle.com
- Cpujan2022 (opens in a new tab)oracle.com
- Vulnerabilities 24 (opens in a new tab)apache.org
- JVN51106450 (opens in a new tab)jvn.jp
- Apache HTTP Server 2.4.50 Path Traversal Code Execution (opens in a new tab)packetstormsecurity.com
Does CVE-2021-42013 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
It was found that the fix for CVE-2021-41773 in Apache HTTP Server 2.4.50 was insufficient. An attacker could use a path traversal attack to map URLs to file...
- Matched to
- HTTP Server on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2021-42013 is a critical-severity flaw in HTTP Server from Apache, published on 7 October 2021. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2021-42013 is 90 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at over 99%.
For HTTP Server from Apache: 2.4.49, 2.4.50. The record lists 6 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.