Advisories
This weekExploitable · Confirmed

github.com/snapcore/snapd: CVE-2024-5138: snapd snapctl auth bypass

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

github.com/snapcore/snapd (Go)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • github.com/snapcore/snapd (Go): from 2.51.6, before 2.63.1
  • github.com/snapcore/snapd (Go): every version, before 0.0.0-20240524114846-68ee9c6aa916
  • github.com/snapcore/snapd (Go): every version, with no fixed release listed

The fix

  • github.com/snapcore/snapd (Go) fixed in 2.63.1

    go
    go get github.com/snapcore/snapd@v2.63.1
    Check what is installed
    go list -m github.com/snapcore/snapd
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/snapcore/snapd to 2.63.1 or the nearest later release, to fix CVE-2024-5138. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • github.com/snapcore/snapd (Go) fixed in 0.0.0-20240524114846-68ee9c6aa916

    go
    go get github.com/snapcore/snapd@v0.0.0-20240524114846-68ee9c6aa916
    Check what is installed
    go list -m github.com/snapcore/snapd
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Go dependency github.com/snapcore/snapd to 0.0.0-20240524114846-68ee9c6aa916 or the nearest later release, to fix CVE-2024-5138. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))