Skip to content

Yamcs API Directory Traversal vulnerability

Critical severity GitHub Reviewed Published Oct 19, 2023 to the GitHub Advisory Database • Updated Nov 12, 2023

Package

maven org.yamcs:yamcs (Maven)

Affected versions

< 5.8.7

Patched versions

5.8.7

Description

Directory Traversal vulnerability in the storage functionality of the API in Yamcs 5.8.6 allows attackers to delete arbitrary files via crafted HTTP DELETE request.

References

Published by the National Vulnerability Database Oct 19, 2023
Published to the GitHub Advisory Database Oct 19, 2023
Reviewed Oct 19, 2023
Last updated Nov 12, 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
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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:U/C:N/I:H/A:H

EPSS score

0.109%
(45th percentile)

Weaknesses

CVE ID

CVE-2023-45278

GHSA ID

GHSA-43fw-536j-w37j

Source code

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