AuthdApplication · Canonical
CVE-2024-9313
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 · uneditedAuthd 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.
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 confidenceThe authd PAM module before version 0.3.5 contains an authorization flaw where broker-managed users can impersonate any other user managed by the same broker. This allows a lower-privilege user to authenticate as any other broker-managed user and execute arbitrary PAM operations, effectively enabling privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AuthdApplication
< 0.3.5CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Authd PAM module is installedRun 'dpkg -l | grep authd' or 'rpm -qa | grep authd' depending on your package manager. On systems using PAM, also check '/lib/security/pam_authd.so' or '/lib64/security/pam_authd.so' for the PAM module binary.Affected if Authd PAM module is present on the system
-
Determine installed Authd versionRun 'dpkg -l authd' or 'rpm -q authd' to get the exact version number. Compare it against version 0.3.5.Affected if The installed version is earlier than 0.3.5 (e.g., 0.3.4, 0.3.3, etc.)
-
Verify broker configuration is in useInspect Authd configuration files in '/etc/authd.conf' or '/etc/authd/' directory for broker-related settings. Check for 'broker' or 'brokers' configuration sections that define user management through a broker.Affected if Authd is configured to use broker-based user management, meaning users are managed by a broker rather than local system accounts
-
Check broker configuration for user impersonation settingsReview the broker configuration file (typically in '/etc/authd/' or as specified in authd.conf) for any settings that control user impersonation or delegation between broker-managed users.Affected if Broker configuration allows or does not restrict impersonation between different broker-managed users
The system is affected if Authd PAM module version is earlier than 0.3.5 AND the broker-based user management feature is enabled, allowing a broker-managed user to impersonate other broker-managed users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.3.5
Upgrade the authd PAM module to version 0.3.5 or later to remediate this vulnerability.
0.3.5
- Upgrade Authd to version 0.3.5 or later
- Verify the installation by checking the Authd version
- Test that PAM operations work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Authd
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-9313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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