Every CVE Search/ Get API key

CVE-2024-9313

PAM module may allow accessing with the credentials of another user

8.8 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
High
Availability
High

Exploit likelihood

0.58%Up 0.5 points since Oct 4, 2024
90%50%10%1%

What each source reports

CVE List Score used 8.8

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.

Record
CVE-2024-9313
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
EUVDEUVD-2024-3161 8.8

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.

Record
EUVD-2024-3161
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-03
GitHub AdvisoriesGHSA-x5q3-c8rm-w787 8.7

PAM module may allow accessing with the credentials of another user

Authd PAM module up to version 0.3.4 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.

This is possible using tools such as su, sudo or ssh (and potentially others) that, so far, do not ensure that the PAM user at the end of the transaction is matching the one who initiated the transaction.

Authd 0.3.5 fixes this by not allowing changing the user unless it was never set before in the PAM stack.

su version that will include https://github.com/util-linux/util-linux/pull/3206 will not be affected ssh version that will include https://github.com/openssh/openssh-portable/pull/521 will not be affected sudo version that will include https://github.com/sudo-project/sudo/pull/412 will not be affected login not affected passwd not affected

<details> <summary>Old report</summary>

Summary

An user can access as another user using its own credentials

Details

I feel we’ve a security issue that is due to the fact that we allow changing the user in the cases in which that’s already provided by PAM, I’ve not tested this using the entra-id broker but it’s reproducible with the example one, but unless I’m missing something it should be independent from the broker in use.

Basically, by going to the user selection page we allow to login as any user by entering the use own credentials.

See for example: https://asciinema.org/a/VIcjpDImomaGu0wxsJJxNdmlf or https://asciinema.org/a/CV3D1gaEhn2yclqSMKCnifYPo

Basically it’s possible to logging in as user1 using the credentials of user2 or user3.

The issue doesn’t affect login or passwd, but it does affect su and sshd, since in both cases they don’t check if the PAM_USER changed before the final authentication.

Now, while those tools should likely be fixed to only read the PAM_USER once pam gave them the final ok, I think authd should not allow changing the user at all when it has been provided by PAM.

</details>

Record
GHSA-x5q3-c8rm-w787
CVSS 4.0
8.7 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-287
Updated
2026-11-02
NVD 8.8

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.

Record
CVE-2024-9313
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSV 8.8

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.

Record
CVE-2024-9313
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Updated
2026-11-02
OSVGHSA-x5q3-c8rm-w787 8.7

PAM module may allow accessing with the credentials of another user

Authd PAM module up to version 0.3.4 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.

This is possible using tools such as su, sudo or ssh (and potentially others) that, so far, do not ensure that the PAM user at the end of the transaction is matching the one who initiated the transaction.

Authd 0.3.5 fixes this by not allowing changing the user unless it was never set before in the PAM stack.

su version that will include https://github.com/util-linux/util-linux/pull/3206 will not be affected ssh version that will include https://github.com/openssh/openssh-portable/pull/521 will not be affected sudo version that will include https://github.com/sudo-project/sudo/pull/412 will not be affected login not affected passwd not affected

<details> <summary>Old report</summary>

Summary

An user can access as another user using its own credentials

Details

I feel we’ve a security issue that is due to the fact that we allow changing the user in the cases in which that’s already provided by PAM, I’ve not tested this using the entra-id broker but it’s reproducible with the example one, but unless I’m missing something it should be independent from the broker in use.

Basically, by going to the user selection page we allow to login as any user by entering the use own credentials.

See for example: https://asciinema.org/a/VIcjpDImomaGu0wxsJJxNdmlf or https://asciinema.org/a/CV3D1gaEhn2yclqSMKCnifYPo

Basically it’s possible to logging in as user1 using the credentials of user2 or user3.

The issue doesn’t affect login or passwd, but it does affect su and sshd, since in both cases they don’t check if the PAM_USER changed before the final authentication.

Now, while those tools should likely be fixed to only read the PAM_USER once pam gave them the final ok, I think authd should not allow changing the user at all when it has been provided by PAM.

</details>

Record
GHSA-x5q3-c8rm-w787
CVSS 4.0
8.7 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
8.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness
CWE-287
Updated
2026-11-02
Show 5 moreShow less
OSVGO-2024-3181 No score

PAM module may allow accessing with the credentials of another user in github.com/ubuntu/authd

PAM module may allow accessing with the credentials of another user in github.com/ubuntu/authd

Record
GO-2024-3181
Updated
2026-11-02
OSVopenSUSE-SU-2024:0350-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20241104T154416 2024-11-04T15:44:16Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3233 CVE-2024-46872 GHSA-762g-9p7f-mrww
    • GO-2024-3234 CVE-2024-47401 GHSA-762v-rq7q-ff97
    • GO-2024-3235 CVE-2024-50052 GHSA-g376-m3h3-mj4r
    • GO-2024-3237 CVE-2024-0133 GHSA-f748-7hpg-88ch
    • GO-2024-3239 CVE-2024-0132 GHSA-mjjw-553x-87pq
    • GO-2024-3240 CVE-2024-10452 GHSA-66c4-2g2v-54qw
    • GO-2024-3241 CVE-2024-10006 GHSA-5c4w-8hhh-3c3h
    • GO-2024-3242 CVE-2024-10086 GHSA-99wr-c2px-grmh
    • GO-2024-3243 CVE-2024-10005 GHSA-chgm-7r52-whjj

  • Update to version 0.0.20241101T215616 2024-11-01T21:56:16Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3244 CVE-2024-50354 GHSA-cph5-3pgr-c82g
    • GO-2024-3245 CVE-2024-39720
    • GO-2024-3246 CVE-2024-8185 GHSA-g233-2p4r-3q7v

  • Update to version 0.0.20241030T212825 2024-10-30T21:28:25Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3230 CVE-2024-48921 GHSA-qjvc-p88j-j9rm
    • GO-2024-3232 CVE-2024-10241 GHSA-6mvp-gh77-7vwh

  • Update to version 0.0.20241030T160108 2024-10-30T16:01:08Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3226 CVE-2024-47827 GHSA-ghjw-32xw-ffwr
    • GO-2024-3227 CVE-2024-10214 GHSA-hm57-h27x-599c
    • GO-2024-3228 GHSA-wcx9-ccpj-hx3c

  • Packaging improvments:

    • Backfill CVE aliases in recent changelog entries

  • Update to version 0.0.20241028T152002 2024-10-28T15:20:02Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3207 GHSA-p5wf-cmr4-xrwr
    • GO-2024-3208 CVE-2024-47825 GHSA-3wwx-63fv-pfq6
    • GO-2024-3210 CVE-2024-8901
    • GO-2024-3211 CVE-2024-50312
    • GO-2024-3212 GHSA-rjfv-pjvx-mjgv
    • GO-2024-3213 CVE-2024-49380
    • GO-2024-3214 CVE-2024-49381
    • GO-2024-3215 CVE-2024-9264 GHSA-q99m-qcv4-fpm7
    • GO-2024-3216 CVE-2024-49753 GHSA-6cf5-w9h3-4rqv
    • GO-2024-3217 CVE-2024-49757 GHSA-3rmw-76m6-4gjc
    • GO-2024-3219 GHSA-7h65-4p22-39j6
    • GO-2024-3220 CVE-2023-32197 GHSA-7h8m-pvw3-5gh4
    • GO-2024-3221 CVE-2024-22036 GHSA-h99m-6755-rgwc
    • GO-2024-3222 GHSA-x7xj-jvwp-97rv
    • GO-2024-3223 CVE-2022-45157 GHSA-xj7w-r753-vj8v
    • GO-2024-3224 CVE-2024-39223 GHSA-8wxx-35qc-vp6r

  • Update to version 0.0.20241017T153730 date 2024-10-17T15:37:30Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3189 CVE-2024-38365 GHSA-27vh-h6mc-q6g8
    • GO-2024-3203 CVE-2024-9486
    • GO-2024-3204 CVE-2024-9594

    Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3189 CVE-2024-38365 GHSA-27vh-h6mc-q6g8
    • GO-2024-3196 CVE-2024-47877 GHSA-8rm2-93mq-jqhc
    • GO-2024-3199 GHSA-vv6c-69r6-chg9
    • GO-2024-3200 CVE-2024-48909 GHSA-3c32-4hq9-6wgj
    • GO-2024-3201 CVE-2023-22644 Go CVE Numbering Authority IDs added or updated with aliases:
    • GO-2024-3166 CVE-2024-47534 GHSA-4f8r-qqr9-fq8j
    • GO-2024-3171 CVE-2024-9341 GHSA-mc76-5925-c5p6 Go CVE Numbering Authority IDs added or updated with aliases:
    • GO-2024-3161 CVE-2024-22030 GHSA-h4h5-9833-v2p4
    • GO-2024-3162 CVE-2024-7594 GHSA-jg74-mwgw-v6x3
    • GO-2024-3163 CVE-2024-47182
    • GO-2024-3164 CVE-2024-47003 GHSA-59hf-mpf8-pqjh
    • GO-2024-3166 CVE-2024-47534 GHSA-4f8r-qqr9-fq8j
    • GO-2024-3167 CVE-2024-9355 GHSA-3h3x-2hwv-hr52
    • GO-2024-3168 CVE-2024-8975 GHSA-chqx-36rm-rf8h
    • GO-2024-3169 CVE-2024-9407 GHSA-fhqq-8f65-5xfc
    • GO-2024-3170 CVE-2024-8996 GHSA-m5gv-m5f9-wgv4
    • GO-2024-3172 CVE-2024-33662 GHSA-9mjw-79r6-c9m8
    • GO-2024-3173 CVE-2024-7558 GHSA-mh98-763h-m9v4
    • GO-2024-3174 CVE-2024-8037 GHSA-8v4w-f4r9-7h6x
    • GO-2024-3175 CVE-2024-8038 GHSA-xwgj-vpm9-q2rq
    • GO-2024-3179 CVE-2024-47616 GHSA-r7rh-jww5-5fjr
    • GO-2024-3181 CVE-2024-9313 GHSA-x5q3-c8rm-w787
    • GO-2024-3182 GHSA-wpr2-j6gr-pjw9 *…
Record
openSUSE-SU-2024:0350-1
Updated
2026-11-02
OSVopenSUSE-SU-2024:14447-1 No score

govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

These are all security issues fixed in the govulncheck-vulndb-0.0.20241030T212825-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2024:14447-1
Updated
2026-11-02
OSVSUSE-SU-2024:3911-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

Update to version 0.0.20241030T212825 2024-10-30T21:28:25Z ( jsc#PED-11136 )

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3230 CVE-2024-48921 GHSA-qjvc-p88j-j9rm
    • GO-2024-3232 CVE-2024-10241 GHSA-6mvp-gh77-7vwh

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3226 CVE-2024-47827 GHSA-ghjw-32xw-ffwr
    • GO-2024-3227 CVE-2024-10214 GHSA-hm57-h27x-599c
    • GO-2024-3228 GHSA-wcx9-ccpj-hx3c

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3207 GHSA-p5wf-cmr4-xrwr
    • GO-2024-3208 CVE-2024-47825 GHSA-3wwx-63fv-pfq6
    • GO-2024-3210 CVE-2024-8901
    • GO-2024-3211 CVE-2024-50312
    • GO-2024-3212 GHSA-rjfv-pjvx-mjgv
    • GO-2024-3213 CVE-2024-49380
    • GO-2024-3214 CVE-2024-49381
    • GO-2024-3215 CVE-2024-9264 GHSA-q99m-qcv4-fpm7
    • GO-2024-3216 CVE-2024-49753 GHSA-6cf5-w9h3-4rqv
    • GO-2024-3217 CVE-2024-49757 GHSA-3rmw-76m6-4gjc
    • GO-2024-3219 GHSA-7h65-4p22-39j6
    • GO-2024-3220 CVE-2023-32197 GHSA-7h8m-pvw3-5gh4
    • GO-2024-3221 CVE-2024-22036 GHSA-h99m-6755-rgwc
    • GO-2024-3222 GHSA-x7xj-jvwp-97rv
    • GO-2024-3223 CVE-2022-45157 GHSA-xj7w-r753-vj8v
    • GO-2024-3224 CVE-2024-39223 GHSA-8wxx-35qc-vp6r

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3189 CVE-2024-38365 GHSA-27vh-h6mc-q6g8
    • GO-2024-3203 CVE-2024-9486
    • GO-2024-3204 CVE-2024-9594

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3189 CVE-2024-38365 GHSA-27vh-h6mc-q6g8
    • GO-2024-3196 CVE-2024-47877 GHSA-8rm2-93mq-jqhc
    • GO-2024-3199 GHSA-vv6c-69r6-chg9
    • GO-2024-3200 CVE-2024-48909 GHSA-3c32-4hq9-6wgj
    • GO-2024-3201 CVE-2023-22644

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3166 CVE-2024-47534 GHSA-4f8r-qqr9-fq8j
    • GO-2024-3171 CVE-2024-9341 GHSA-mc76-5925-c5p6

  • Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-3161 CVE-2024-22030 GHSA-h4h5-9833-v2p4
    • GO-2024-3162 CVE-2024-7594 GHSA-jg74-mwgw-v6x3
    • GO-2024-3163 CVE-2024-47182
    • GO-2024-3164 CVE-2024-47003 GHSA-59hf-mpf8-pqjh
    • GO-2024-3166 CVE-2024-47534 GHSA-4f8r-qqr9-fq8j
    • GO-2024-3167 CVE-2024-9355 GHSA-3h3x-2hwv-hr52
    • GO-2024-3168 CVE-2024-8975 GHSA-chqx-36rm-rf8h
    • GO-2024-3169 CVE-2024-9407 GHSA-fhqq-8f65-5xfc
    • GO-2024-3170 CVE-2024-8996 GHSA-m5gv-m5f9-wgv4
    • GO-2024-3172 CVE-2024-33662 GHSA-9mjw-79r6-c9m8
    • GO-2024-3173 CVE-2024-7558 GHSA-mh98-763h-m9v4
    • GO-2024-3174 CVE-2024-8037 GHSA-8v4w-f4r9-7h6x
    • GO-2024-3175 CVE-2024-8038 GHSA-xwgj-vpm9-q2rq
    • GO-2024-3179 CVE-2024-47616 GHSA-r7rh-jww5-5fjr
    • GO-2024-3181 CVE-2024-9313 GHSA-x5q3-c8rm-w787
    • GO-2024-3182 GHSA-wpr2-j6gr-pjw9
    • GO-2024-3184 CVE-2024-36814 GHSA-9cp9-8gw2-8v7m
    • GO-2024-3185 CVE-2024-47832
    • GO-2024-3186 CVE-2024-9675 GHSA-586p-749j-fhwp
    • GO-2024-3188 CVE-2024-9312 GHSA-4gfw-wf7c-w6g2
    • GO-2024-3190 CVE-2024-47067 GHSA-8pph-gfhp-w226
    • GO-2024-3191 CVE-2024-9180 GHSA-rr8j-7w34-xp5j
Record
SUSE-SU-2024:3911-1
Updated
2026-11-02
OSVSUSE-SU-2025:0429-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20250207T224745 2025-02-07T22:47:45Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3456 CVE-2025-24786 GHSA-9r4c-jwx3-3j76
    • GO-2025-3457 CVE-2025-24787 GHSA-c7w4-9wv8-7x7c
    • GO-2025-3458 CVE-2025-24366 GHSA-vj7w-3m8c-6vpx

  • Update to version 0.0.20250206T175003 2025-02-06T17:50:03Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2023-1867 CVE-2022-47930 GHSA-c58h-qv6g-fw74
    • GO-2024-3244 CVE-2024-50354 GHSA-cph5-3pgr-c82g

  • Update to version 0.0.20250206T165438 2025-02-06T16:54:38Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3428 CVE-2025-22867
    • GO-2025-3447 CVE-2025-22866

  • Update to version 0.0.20250205T232745 2025-02-05T23:27:45Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3408
    • GO-2025-3448 GHSA-23qp-3c2m-xx6w
    • GO-2025-3449 GHSA-mx2j-7cmv-353c
    • GO-2025-3450 GHSA-w7wm-2425-7p2h
    • GO-2025-3454 GHSA-mj4v-hp69-27x5
    • GO-2025-3455 GHSA-vqv5-385r-2hf8

  • Update to version 0.0.20250205T003520 2025-02-05T00:35:20Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3451

  • Update to version 0.0.20250204T220613 2025-02-04T22:06:13Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2025-3431 CVE-2025-24884 GHSA-hcr5-wv4p-h2g2
    • GO-2025-3433 CVE-2025-23216 GHSA-47g2-qmh2-749v
    • GO-2025-3434 CVE-2025-24376 GHSA-fc89-jghx-8pvg
    • GO-2025-3435 CVE-2025-24784 GHSA-756x-m4mj-q96c
    • GO-2025-3436 CVE-2025-24883 GHSA-q26p-9cq4-7fc2
    • GO-2025-3437 GHSA-274v-mgcv-cm8j
    • GO-2025-3438 CVE-2024-11741 GHSA-wxcc-2f3q-4h58
    • GO-2025-3442 CVE-2025-24371 GHSA-22qq-3xwm-r5x4
    • GO-2025-3443 GHSA-r3r4-g7hq-pq4f
    • GO-2025-3444 CVE-2024-35177
    • GO-2025-3445 CVE-2024-47770

  • Use standard RPM macros to unpack the source and populate a working directory. Fixes build with RPM 4.20.

  • Update to version 0.0.20250130T185858 2025-01-30T18:58:58Z. Refs jsc#PED-11136 Go CVE Numbering Authority IDs added or updated with aliases:

    • GO-2024-2842 CVE-2024-3727 GHSA-6wvf-f2vw-3425
    • GO-2024-3181 CVE-2024-9313 GHSA-x5q3-c8rm-w787
    • GO-2024-3188 CVE-2024-9312 GHSA-4gfw-wf7c-w6g2
    • GO-2025-3372 CVE-2024-45339 GHSA-6wxm-mpqj-6jpf
    • GO-2025-3373 CVE-2024-45341
    • GO-2025-3383 CVE-2024-45340
    • GO-2025-3408
    • GO-2025-3412 CVE-2024-10846 GHSA-36gq-35j3-p9r9
    • GO-2025-3420 CVE-2024-45336
    • GO-2025-3421 CVE-2025-22865
    • GO-2025-3424 CVE-2025-24369
    • GO-2025-3426 CVE-2025-0750 GHSA-hp5j-2585-qx6g
    • GO-2025-3427 CVE-2024-13484 GHSA-58fx-7v9q-3g56
Record
SUSE-SU-2025:0429-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/ubuntu/authd
Go
 before 0.0.0-20240930103526-63e527496b01
0.0.0-20240930103526-63e527496b01
github.com/ubuntu/authd
Go
 0.1.0 up to 0.3.5
0.3.5
github.com/ubuntu/authd
Go
 before 0.3.5
0.3.5
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP5
From an advisory covering 44 CVEs
 before 0.0.20241030T212825-150000.1.9.1
0.0.20241030T212825-150000.1.9.1
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP6
From an advisory covering 44 CVEs
 before 0.0.20241030T212825-150000.1.9.1
0.0.20241030T212825-150000.1.9.1
govulncheck-vulndb
openSUSE:Leap 15.5
From an advisory covering 44 CVEs
 before 0.0.20241030T212825-150000.1.9.1
0.0.20241030T212825-150000.1.9.1
govulncheck-vulndb
openSUSE:Leap 15.6
From an advisory covering 44 CVEs
 before 0.0.20241030T212825-150000.1.9.1
0.0.20241030T212825-150000.1.9.1
govulncheck-vulndb
SUSE:Linux Enterprise Module for Package Hub 15 SP6
From an advisory covering 28 CVEs
 before 0.0.20250207T224745-150000.1.32.1
0.0.20250207T224745-150000.1.32.1
govulncheck-vulndb
openSUSE:Leap 15.6
From an advisory covering 28 CVEs
 before 0.0.20250207T224745-150000.1.32.1
0.0.20250207T224745-150000.1.32.1
govulncheck-vulndb
SUSE:Package Hub 12
From an advisory covering 56 CVEs
 before 0.0.20241104T154416-5.1
0.0.20241104T154416-5.1
govulncheck-vulndb
openSUSE:Tumbleweed
From an advisory covering 44 CVEs
 before 0.0.20241030T212825-1.1
0.0.20241030T212825-1.1

History

History
RecordedChangedSources
affected, facts
aliases, publishedEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2024-9313 is a high vulnerability (CVSS 8.8) in Canonical Authd, published October 3, 2024. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.58%, the 47th percentile. Fixed in github.com/ubuntu/authd 0.0.0-20240930103526-63e527496b01.

References

Show 87 moreShow less
This page doesn't list everything

Left out here: the rest of 1 source description. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open