dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2024-24783

MEDIUM · 5.9 CVSS v3.1 Published 2024-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability causes Certificate.Verify in crypto/tls to panic when verifying a certificate chain containing a certificate with an unknown public key algorithm. This affects all Go TLS clients and TLS servers configured with ClientAuth set to VerifyClientCertIfGiven or RequireAndVerifyClientCert, creating a denial-of-service condition via panic.

MitigationUpdate to a patched Go version once available. Until then, ensure all certificates in the chain use standard, recognized public key algorithms (RSA, ECDSA, Ed25519).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Go version
    Run 'go version' to see the Go runtime version
    Affected if Version is before Go 1.22.3 or between 1.22.0-1.22.2, or before Go 1.21.10 (1.21.0-1.21.9)
  2. Identify TLS server configuration
    Review your TLS server code and config for ClientAuth setting - look for VerifyClientCertIfGiven or RequireAndVerifyClientCert values in tls.Config.ClientAuth
    Affected if Your Go application runs a TLS server with ClientAuth set to VerifyClientCertIfGiven or RequireAndVerifyClientCert, AND runs a vulnerable Go version
  3. Identify TLS client usage
    Search codebase for tls.Client() calls or http.Client with custom Transport making HTTPS connections
    Affected if Your Go application makes outbound TLS connections to servers you do not control, AND runs a vulnerable Go version
  4. Review certificate sources
    Identify all certificate chains your application verifies - check client certificates you accept and server certificates you connect to
    Affected if Any certificate in your trusted chains uses a non-standard or unknown public key algorithm (not RSA, ECDSA, or Ed25519)

You are affected if running a Go version before 1.22.3 or 1.21.10 AND your application either acts as a TLS server with client certificate verification or makes outbound TLS connections to potentially untrusted servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched Go version once available. Until then, ensure all certificates in the chain use standard, recognized public key algorithms (RSA, ECDSA, Ed25519).

Recommended fix High confidence

Go 1.22.3 or later (or appropriate backported security release for older Go versions)

  1. Upgrade Go to version 1.22.3 or later to patch the NULL pointer dereference in crypto/tls Certificate.Verify
  2. For systems using older Go versions, apply the backported security patches if available from your Go distribution vendor
  3. After upgrading, verify that TLS certificate verification no longer panics when encountering certificates with unknown public key algorithms
  4. Test TLS functionality, especially certificate verification in both client and server configurations
  5. Ensure that Config.ClientAuth settings are reviewed - servers using VerifyClientCertIfGiven or RequireAndVerifyClientCert are affected
Caveat Upgrading Go minor versions may introduce subtle behavioral changes in other packages; thoroughly test TLS functionality after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24783 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data