What is CVE-2018-1301?A medium-severity flaw in HTTP Server, explained.
CVE-2018-1301 is a medium-severity flaw (CVSS 5.9) in HTTP Server from Apache, published on 26 March 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 15%. If you run an affected version, plan in the vendor’s fix.
Published 26 March 2018. Record last updated 7 November 2023. We keep this page's data up to date.
What is CVE-2018-1301? 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 take it offline.
A specially crafted request could have crashed the Apache HTTP Server prior to version 2.4.30, due to an out of bound access after a size limit is reached by reading the HTTP header. This vulnerability is considered very hard if not impossible to trigger in non-debug mode (both log and build level), so it is classified as low risk for common server usage.
What kind of flaw is it?
- CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
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 offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2018-1301 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 15%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2018-1301 scores 35. Action: Monitor.
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-2018-1301 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-2018-1301? 8 products.
The published record lists 8 products from 5 vendors. If you run one of these, check your version, then go to the fix below.
- Application
HTTP Server
by Apache
Affected versionsup to 2.4.29 - Operating system
Enterprise Linux
by Red Hat
Affected versions6.07.07.47.57.6 - Operating system
Ubuntu Linux
by Canonical
Affected versions12.0414.0416.0417.1018.04 - Operating system
Debian Linux
by Debian
Affected versions7.08.09.0 - Operating system
Clustered Data Ontap
by Netapp
Affected versionsversion not specified - Application
Santricity Cloud Connector
by Netapp
Affected versionsversion not specified - Application
Storage Automation Store
by Netapp
Affected versionsversion not specified - Application
Storagegrid
by Netapp
Affected versionsversion not specified
How do I fix CVE-2018-1301? 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 advisory 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.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
28 links- Vulnerabilities 24 (opens in a new tab)apache.org
- oss-security mailing list post, 24 Mar 2018 (opens in a new tab)openwall.com · 2018
- Web page (opens in a new tab)securityfocus.com
- Web page (opens in a new tab)securitytracker.com
- RHSA 2018:3558 (opens in a new tab)redhat.com
- RHSA 2019:0366 (opens in a new tab)redhat.com
Does CVE-2018-1301 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 new flaw affects software Acme tracks
A specially crafted request could have crashed the Apache HTTP Server prior to version 2.4.30, due to an out of bound access after a size limit is reached by...
- Matched to
- HTTP Server on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-1301 is a medium-severity flaw in HTTP Server from Apache, published on 26 March 2018. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2018-1301 is 35 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 15%. That can change at any time, which is why we keep watching.
For HTTP Server from Apache: up to 2.4.29. The record lists 8 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.