You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will illustrate some nice false positives in go based on the vulnerable functions not being called. We use govulncheck to get the following:
Scanning for dependencies with known vulnerabilities...
No vulnerabilities found.
=== Informational ===
The vulnerabilities below are in packages that you import, but your code
doesn't appear to call any vulnerable functions. You may not need to take any
action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
for details.
Vulnerability #1: GO-2022-0968
Unauthenticated clients can cause a panic in SSH servers. When
using AES-GCM or ChaCha20Poly1305, consuming a malformed packet
which contains an empty plaintext causes a panic.
Found in: golang.org/x/crypto/[email protected]
Fixed in: golang.org/x/crypto/[email protected]
More info: https://pkg.go.dev/vuln/GO-2022-0968
Vulnerability #2: GO-2022-0493
When called with a non-zero flags parameter, the Faccessat
function can incorrectly report that a file is accessible.
Found in: golang.org/x/sys/[email protected]
Fixed in: golang.org/x/sys/[email protected]
More info: https://pkg.go.dev/vuln/GO-2022-0493
Vulnerability #3: GO-2021-0356
Attackers can cause a crash in SSH servers when the server has
been configured by passing a Signer to ServerConfig.AddHostKey
such that 1) the Signer passed to AddHostKey does not implement
AlgorithmSigner, and 2) the Signer passed to AddHostKey returns
a key of type “ssh-rsa” from its PublicKey method. Servers
that only use Signer implementations provided by the ssh package
are unaffected.
Found in: golang.org/x/crypto/[email protected]
Fixed in: golang.org/x/crypto/[email protected]
More info: https://pkg.go.dev/vuln/GO-2021-0356
So from that all of the following should be added as FP's:
This will illustrate some nice false positives in go based on the vulnerable functions not being called. We use
govulncheck
to get the following:So from that all of the following should be added as FP's:
And the standard protobuf ones:
The text was updated successfully, but these errors were encountered: