Skip to content

Insecure temporary file in Netflix OSS Hollow

Moderate severity GitHub Reviewed Published Mar 29, 2021 to the GitHub Advisory Database • Updated Aug 8, 2023

Package

maven com.netflix.hollow:hollow (Maven)

Affected versions

<= 6.1.0

Patched versions

None

Description

ID: NFLX-2021-001
Title: Local information disclosure in Hollow
Release Date: 2021-03-23
Credit: Security Researcher @JLLeitschuh

Overview

Security researcher @JLLeitschuh reported that Netflix Hollow (a Netflix OSS project available here: https://github.com/Netflix/hollow) writes to a local temporary directory before validating the permissions on it.

Impact

An attacker with the ability to create directories and set permissions on the local filesystem could pre-create this directory and read or modify anything written there by the Hollow process.

Description

Since the Files.exists(parent) is run before creating the directories, an attacker can pre-create these directories with wide permissions. Additionally, since an insecure source of randomness is used, the file names to be created can be deterministically calculated.

Workarounds and Fixes

Avoid running Hollow in configurations that share a filesystem with less-trusted processes. May be fixed in a future release.

References

Published by the National Vulnerability Database Mar 23, 2021
Reviewed Mar 24, 2021
Published to the GitHub Advisory Database Mar 29, 2021
Last updated Aug 8, 2023

Severity

Moderate

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
Low
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.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2021-28099

GHSA ID

GHSA-9295-mhf3-v33m

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.