Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/fkie-cad/yapscan >= 0.18.0, < 0.19.2
Fixed in
0.19.2· Vendor fix available
Issue
Impact If you use the report server, it may be vulnerable to a Denial of Service attack. Patches Has been patched in v0.19.2. References The vulnerability was inherited by the following upstream vulnerabilites - golang.org/x/text < v0.3.7 - golang.org/x/net < 0.0.0-20220906165146-f3363e06e74c
Recommended action: Upgrade to 0.19.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/fkie-cad/yapscan >= 0.18.0, < 0.19.1
Fixed in
0.19.1· Vendor fix available
Issue
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.
Recommended action: Upgrade to 0.19.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.