What is the CVSS score of CVE-2017-8418?

CVE-2017-8418 has a CVSS 3.0 base score of 3.3 (Low). CVSS vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for CVE-2017-8418?

Yes, a public proof-of-concept exploit is available for CVE-2017-8418. Prioritise patching immediately. EPSS: 0.1%.

Is there a patch available for CVE-2017-8418?

Yes, a patch is available for CVE-2017-8418. Update the affected software to the latest version immediately.

Rubocop CVE-2017-8418

LOW

Exposure of Resource to Wrong Sphere (CWE-668)

2017-05-02 cve@mitre.org

Information Disclosure Rubocop

3.3

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

3.3 LOW

AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

May 02, 2017 - 14:59 cve.org

LOW 3.3

DescriptionCVE.org

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.

AnalysisAI

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. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Exposure of Resource to Wrong Sphere (CWE-668), which allows attackers to access resources from an unintended security context. 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. Affected products include: Rubocop Project Rubocop.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Implement proper access controls, validate resource access permissions, use security boundaries.