Skip to content

RuboCop gem Insecure use of /tmp

Low severity GitHub Reviewed Published Nov 15, 2017 to the GitHub Advisory Database • Updated Aug 28, 2023

Package

bundler rubocop (RubyGems)

Affected versions

< 0.49.0

Patched versions

0.49.0

Description

RuboCop 0.48.1 and earlier does not use /tmp in safe way, allowing local users to exploit this to tamper with cache files belonging to other users.

References

Published to the GitHub Advisory Database Nov 15, 2017
Reviewed Jun 16, 2020
Last updated Aug 28, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.042%
(5th percentile)

Weaknesses

CVE ID

CVE-2017-8418

GHSA ID

GHSA-wmjf-jpjj-9f3j

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.