What is CVE-2015-3315?A high-severity flaw in Automatic Bug Reporting Tool, explained.
CVE-2015-3315 is a high-severity flaw (CVSS 7.8) in Automatic Bug Reporting Tool from Red Hat, published on 26 June 2017. 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 4.8%. If you run an affected version, plan in the vendor’s fix.
Published 26 June 2017. Record last updated 20 April 2025. We keep this page's data up to date.
What is CVE-2015-3315? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
Automatic Bug Reporting Tool (ABRT) allows local users to read, change the ownership of, or have other unspecified impact on arbitrary files via a symlink attack on (1) /var/tmp/abrt/*/maps, (2) /tmp/jvm-*/hs_error.log, (3) /proc/*/exe, (4) /etc/os-release in a chroot, or (5) an unspecified root directory related to librpm.
What kind of flaw is it?
- CWE-59Improper Link Resolution Before File Access ('Link Following')
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- 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.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is CVE-2015-3315 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 4.8%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2015-3315 scores 49. Action: Plan remediation.
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-2015-3315 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-2015-3315? 7 products.
The published record lists 7 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Automatic Bug Reporting Tool
by Red Hat
Affected versionsversion not specified - Operating system
Enterprise Linux Desktop
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Hpc Node
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Hpc Node Eus
by Red Hat
Affected versions7.1 - Operating system
Enterprise Linux Server
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Server Eus
by Red Hat
Affected versions7.1 - Operating system
Enterprise Linux Workstation
by Red Hat
Affected versions7.0
How do I fix CVE-2015-3315? 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.
- 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-2015-3315 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
Automatic Bug Reporting Tool (ABRT) allows local users to read, change the ownership of, or have other unspecified impact on arbitrary files via a symlink at...
- Matched to
- Automatic Bug Reporting Tool 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-2015-3315 is a high-severity flaw in Automatic Bug Reporting Tool from Red Hat, published on 26 June 2017. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2015-3315 is 49 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
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 4.8%. That can change at any time, which is why we keep watching.
For Automatic Bug Reporting Tool from Red Hat: version not specified. The record lists 7 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.