CVE-2017-8418

low
Published 2017-05-01 ยท Modified 2024-02-16
CVSS v3
3.3
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
3.3

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.

Predictions

Exploit likelihood
34%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Fixed 5 releases
VersionStatusFixed in
trixie Fixed 0.49.1+dfsg-1
sid Fixed 0.49.1+dfsg-1
forky Fixed 0.49.1+dfsg-1
bullseye Fixed 0.49.1+dfsg-1
bookworm Fixed 0.49.1+dfsg-1

Package impact

EcosystemPackageVulnerableFixed
ruby RubyGemsrubocop<>= 0.49.0>= 0.49.0
ruby RubyGemsrubocop<0.49.00.49.0

Application impact

VendorProductVersionsFixed
rubocop_projectrubocop{"endIncluding":"0.48.1"}

References

CWEs

CWE-668

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.