CVE-2024-24783 Affecting go-md2man package, versions <2.0.3-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-GOMD2MAN-6442343
  • published14 Mar 2024
  • disclosed5 Mar 2024

Introduced: 5 Mar 2024

CVE-2024-24783  (opens in a new tab)

How to fix?

Upgrade Chainguard go-md2man to version 2.0.3-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream go-md2man package and not the go-md2man package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Verifying a certificate chain which contains a certificate with an unknown public key algorithm will cause Certificate.Verify to panic. This affects all crypto/tls clients, and servers that set Config.ClientAuth to VerifyClientCertIfGiven or RequireAndVerifyClientCert. The default behavior is for TLS servers to not verify client certificates.

CVSS Scores

version 3.1