Skip to content

ChainerRL Visualizer 0.1.1 vulnerable to Path Traversal via unsafe use of send_file function

Critical severity GitHub Reviewed Published Jul 12, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

pip chainerrl-visualizer (pip)

Affected versions

<= 0.1.1

Patched versions

None

Description

The chainer/chainerrl-visualizer repository through 0.1.1 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.

References

Published by the National Vulnerability Database Jul 11, 2022
Published to the GitHub Advisory Database Jul 12, 2022
Reviewed Jul 21, 2022
Last updated Jan 27, 2023

Severity

Critical

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
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

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:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

EPSS score

0.238%
(63rd percentile)

Weaknesses

CVE ID

CVE-2022-31573

GHSA ID

GHSA-687h-86vc-5x59
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.