GitHub Advisoryadvisory · Go

GHSA-9h6h-9g78-86f7 Yapscan's report receiver server vulnerable to path traversal and log injection

HIGH Published 2022-12-29 Modified 2022-12-29 Official page ↗
Ecosystem
Go
Packages
github.com/fkie-cad/yapscan
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-117, CWE-22, CWE-73
Reviewed
2022-12-29

Affected packages

• Go github.com/fkie-cad/yapscan: >= 0.18.0, < 0.19.1 → fixed in 0.19.1

Description

Impact If you make use of the report receiver server (experimental), a client may be able to forge requests such that arbitrary files on the host can be overwritten (subject to permissions of the yapscan server), leading to loss of data. This is particularly problematic if you do not authenticate clients and/or run the server with elevated permissions. Patches Vulnerable versions: • v0.18.0 • v0.19.0 (unreleased) This problem is patched in version v0.19.1 Workarounds Update to the newer version is highly encouraged! Measures to reduce the risk of this include authenticating clients (see `--client-ca` flag) and containerization of the yapscan server. References The tracking issue is #35. There you can find the commits, fixing the issue.

Related

Weakness · CWE (3)

  • CWE-117 Improper Output Neutralization for Logs weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness
  • CWE-73 External Control of File Name or Path weakness

References