What is CVE-2018-3760?A high-severity flaw in Sprockets, explained.
CVE-2018-3760 is a high-severity flaw (CVSS 7.5) in Sprockets from Sprockets Project, published on 26 June 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 27%. If you run an affected version, plan in the vendor’s fix.
Published 26 June 2018. Record last updated 9 October 2019. We keep this page's data up to date.
What is CVE-2018-3760? 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.
There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted requests can be used to access files that exists on the filesystem that is outside an application's root directory, when the Sprockets server is used in production. All users running an affected release should either upgrade or use one of the work arounds immediately.
What kind of flaw is it?
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor
- 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
Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is CVE-2018-3760 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 27%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
- Exploit likelihood jumped
CVE-2018-3760 scores 81. 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-2018-3760 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-3760? 4 products.
The published record lists 4 products from 3 vendors. If you run one of these, check your version, then go to the fix below.
- Application
Sprockets
Affected versions2.0.0 to 2.12.43.0.0 to 3.7.14.0.0-beta14.0.0-beta24.0.0-beta34.0.0-beta44.0.0-beta54.0.0-beta64.0.0-beta7 - Operating system
Enterprise Linux
by Red Hat
Affected versions6.06.77.07.37.47.5 - Application
Cloudforms
by Red Hat
Affected versions4.54.6 - Operating system
Debian Linux
by Debian
Affected versions9.0
How do I fix CVE-2018-3760? 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.
Does CVE-2018-3760 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
There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted reque...
- Matched to
- Sprockets 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-3760 is a high-severity flaw in Sprockets from Sprockets Project, published on 26 June 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 read data.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2018-3760 is 81 out of 100, which is High. Its action is "Emergency patch". 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 27%. That can change at any time, which is why we keep watching.
For Sprockets from Sprockets Project: 2.0.0 to 2.12.4, 3.0.0 to 3.7.1, 4.0.0-beta1, 4.0.0-beta2, 4.0.0-beta3, 4.0.0-beta4 and 3 more. The record lists 4 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.