Skip to content
Fencer Intel
high 7.5

GHSA-9h6h-9g78-86f7 json

Yapscan's report receiver server vulnerable to path traversal and log injection

published 3y ago modified 8mo ago also GO-2022-1204

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### 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.

Patch / fix

  • go github.com/fkie-cad/yapscan 0.19.1

Is GHSA-9h6h-9g78-86f7 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/fkie-cad/yapscan
>=0.18.0, <0.19.1
0.19.1

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.