How severe is CVE-2024-9313?

CVE-2024-9313 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-9313?

CVE-2024-9313 affects the following packages: github.com/ubuntu/authd (Go), github.com/ubuntu/authd (Go). Ecosystems affected: Go.

How do I fix CVE-2024-9313?

Update github.com/ubuntu/authd to 0.0.0-20240930103526-63e527496b01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9313 is resolved across your whole dependency graph.

How do I detect CVE-2024-9313 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ubuntu/authd. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-9313 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-9313?

O3 pinpoints whether CVE-2024-9313 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-9313 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-9313 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2024-9313 published, and has it been updated?

CVE-2024-9313 was published on October 3, 2024 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

CVE-2024-9313

HIGH

CVE-2024-9313 is a high-severity (CVSS 8.8) vulnerability in github.com/ubuntu/authd. O3 Security confirms whether CVE-2024-9313 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

PAM module may allow accessing with the credentials of another user

Also known asGHSA-x5q3-c8rm-w787GO-2024-3181

Published

Oct 3, 2024

Updated

Jul 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐹github.com/ubuntu/authd🐹github.com/ubuntu/authd

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Authd PAM module before version 0.3.5 can allow broker-managed users to impersonate any other user managed by the same broker and perform any PAM operation with it, including authenticating as them.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ubuntu/authd`	all versions	0.0.0-20240930103526-63e527496b01
🐹Go	`github.com/ubuntu/authd`	≥ 0.1.0&&< 0.3.5	0.3.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ubuntu/authd. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/ubuntu/authd to 0.0.0-20240930103526-63e527496b01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-9313 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-9313 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-9313. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Authd PAM module before version 0.3.5 can allow broker-managed users to impersonate any other user managed by the same broker and perform any PAM operation with it, including authenticating as them.

O3 Security · Impact-Aware SCA

Is CVE-2024-9313 in your dependencies?

O3 detects CVE-2024-9313 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works