# CVE-2024-10963: Pam: improper hostname interpretation in pam_access leads to access control bypass

> Attackers can bypass access controls in pam_access by spoofing hostnames, gaining unauthorized access to services or terminals on affected Linux systems.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Nov 2024
- **Updated:** 13 Oct 2026
- **Also known as:** ALSA-2024:10244, AZL-52539, BELL-CVE-2024-10963, CLSA-2024-1733245591, CLSA-2024-1735300164, DEBIAN-CVE-2024-10963, GHSA-rw99-6hrh-fmjr, OESA-2024-2501, RHSA-2024:10232, RHSA-2024:10244, RLSA-2024:10244, SUSE-SU-2025:20104-1, SUSE-SU-2025:20229-1, UBUNTU-CVE-2024-10963, USN-7761-1, openSUSE-SU-2024:14563-1

## What is CVE-2024-10963?

CVE-2024-10963 is a high-severity authentication bypass vulnerability in Red Hat Enterprise Linux 10, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in pam_access, where certain rules in its configuration file are mistakenly treated as hostnames. This vulnerability allows attackers to trick the system by pretending to be a trusted hostname, gaining unauthorized access. This issue poses a risk for systems that rely on this feature to control who can access certain services or terminals.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-10963?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam` | AlmaLinux:9 | All versions | 1.5.1-22.el9_5 |
| `pam-devel` | AlmaLinux:9 | All versions | 1.5.1-22.el9_5 |
| `pam-docs` | AlmaLinux:9 | All versions | 1.5.1-22.el9_5 |
| `pam-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.5.1-22.el9_5 |
| `pam-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.5.1-22.el9_5 |
| `pam-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.5.1-22.el9_5 |
| `pam-docs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.5.1-22.el9_5 |
| `pam` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.5.1-22.el9_5 |
| `pam-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.5.1-22.el9_5 |
| `pam-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.5.1-22.el9_5 |
| `pam-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.5.1-23.el9_4 |
| `pam-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.5.1-23.el9_4 |
| `pam-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.5.1-23.el9_4 |
| `pam-docs` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:1.5.1-23.el9_4 |
| `pam` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.5.1-23.el9_4 |
| `pam-debuginfo` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.5.1-23.el9_4 |
| `pam-debugsource` | Red Hat:rhel_eus:9.4::baseos | All versions | 0:1.5.1-23.el9_4 |
| `pam` | Rocky Linux:9 | All versions | 0:1.5.1-22.el9_5 |
| `pam` | SUSE:Linux Micro 6.0 | All versions | 1.6.0-4.1 |
| `pam` | SUSE:Linux Micro 6.1 | All versions | 1.6.1-slfo.1.1_2.1 |
| `pam` | openSUSE:Tumbleweed | All versions | 1.7.0-2.1 |

## How do I fix CVE-2024-10963?

Apply the vendor's patch.

## Is CVE-2024-10963 being exploited?

There is no known exploitation of CVE-2024-10963 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10963 and fix it if it is affected.

What it is: CVE-2024-10963 is a high-severity authentication bypass vulnerability in Red Hat Enterprise Linux 10, published on 7 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10963 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10963/ (Markdown: https://insights.sbomify.com/CVE-2024-10963/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10963
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10963
- OSV: https://osv.dev/vulnerability/CVE-2024-10963

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10963/
Summaries are generated and may contain mistakes; the official description above is the record.