x/vulndb: potential Go vuln in github.com/fkie-cad/yapscan: GHSA-9h6h-9g78-86f7

[GoVulnBot]

In GitHub Security Advisory GHSA-9h6h-9g78-86f7, there is a vulnerability in the following Go packages or modules:

Unit	Fixed	Vulnerable Ranges
github.com/fkie-cad/yapscan	0.19.1	>= 0.18.0, < 0.19.1

Cross references: No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: TODO
    versions:
      - introduced: 0.18.0
        fixed: 0.19.1
    packages:
      - package: github.com/fkie-cad/yapscan
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.
ghsas:
  - GHSA-9h6h-9g78-86f7

[gopherbot]

Change https://go.dev/cl/460419 mentions this issue: data/excluded: batch add GO-2022-1253, GO-2022-1251, GO-2022-1250, GO-2022-1248, GO-2022-1245, GO-2022-1243, GO-2022-1240, GO-2022-1239, GO-2022-1236, GO-2022-1235, GO-2022-1225, GO-2022-1220, GO-2022-1219, GO-2022-1218, GO-2022-1216, GO-2022-1208, GO-2022-1206, GO-2022-1204, GO-2022-1200, GO-2022-1192, GO-2022-1190, GO-2022-1189, GO-2022-1258, GO-2022-1226, GO-2022-1214, GO-2022-1210, GO-2022-1212

[gopherbot]

Change https://go.dev/cl/592835 mentions this issue: data/reports: unexclude 50 reports

[gopherbot]

Change https://go.dev/cl/607232 mentions this issue: data/reports: unexclude 20 reports (30)