CVE intelligence and bounded remediation

CVE-2024-3183 — A vulnerability was found in FreeIPA in a way when a Kerberos TGS-REQ is encrypted using the client’s session key

High CVSS 8.1

A vulnerability was found in FreeIPA in a way when a Kerberos TGS-REQ is encrypted using the client’s session key. This key is different for each new session, which protects it from brute force attacks. However, the ticket it contains is encrypted using the target principal key directly. For user principals, this key is a hash of a public per-principal randomly-generated salt and the user’s password. If a principal is compromised it means the attacker would be able to retrieve tickets encrypted to any principal, all of them being encrypted by their own key directly. By taking these tickets and salts offline, the attacker could run brute force attacks to find character strings able to decrypt tickets when combined to a principal salt (i.e. find the principal’s password).

Severity
High
CVSS
8.1 (3.1)
Published
2024-06-12
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-916

Affected products

  • redhat / enterprise_linux / 7.0
  • redhat / enterprise_linux / 8.0
  • redhat / enterprise_linux_aus / 8.2
  • redhat / enterprise_linux_aus / 8.4
  • redhat / enterprise_linux_aus / 8.6
  • redhat / enterprise_linux_eus / 8.8

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.