Security readout for executives and security teams
Plain-English summary
CVE-2024-10963 can cause PAM access rules to mistake certain configuration entries for trusted hostnames. An attacker able to appear as that hostname could bypass intended service or terminal restrictions, risking unauthorized access and serious data compromise.
Executive priority
Treat as a high-priority access-control issue, especially on externally reachable systems using hostname-based pam_access policies. Rapidly identify applicable Red Hat builds and patch them. Systems not using pam_access or hostname-dependent rules likely have lower practical urgency, but require validation rather than assumption.
Technical view
The flaw is an authentication or authorization weakness in pam_access. Its parsing can interpret certain rules as hostnames, enabling a network-based bypass under specific conditions. CVSS 3.1 rates it 7.4: high complexity, no privileges or user interaction required, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Exposure is most likely where a listed Red Hat Enterprise Linux 8, 9, 9.4 EUS, or OpenShift 4.16–4.18 build uses pam_access with hostname-dependent rules. Generic PAM version numbers alone are insufficient to confirm exposure; match vendor packages, builds, configuration, and enabled services.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of exploitation in the wild. Exploitation is network-accessible but rated high complexity, apparently requiring conditions that let an attacker-controlled identity be accepted as a trusted hostname.
Researcher notes
Configuration is central to practical risk. Researchers should distinguish package presence from active pam_access use, map which services invoke it, and examine hostname trust and resolution boundaries. The source bundle identifies upstream issue and pull-request records, but does not establish public weaponization or observed attacks.
Mitigation direction
- Match each installed PAM, RHCOS, or OpenShift build against Red Hat's affected-product data.
- Apply the applicable Red Hat security erratum for the exact product and release.
- Prioritize services whose PAM access controls depend on hostname interpretation.
- Reduce external exposure of affected authentication services until updates are verified.
- Consult vendor guidance before changing PAM rules; the bundle establishes no specific configuration workaround.
Validation and detection
- Inventory PAM packages and affected OpenShift or RHCOS builds across relevant systems.
- Identify systems actively using pam_access and hostname-dependent access rules.
- Confirm updated package or image builds against the applicable Red Hat erratum.
- Retest intended allow and deny decisions in a controlled environment after remediation.
- Review access records for unexpected successful sessions associated with trusted hostname rules.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-10963 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhatVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Reported to Red Hat.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2024:10232CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:10244CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:10379CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:10518CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:10528CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:10852CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2024:6122CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2024-10963CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2324291CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/linux-pam/linux-pam/issues/834CVE reference, redhat
- https://github.com/linux-pam/linux-pam/pull/835CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.