dbcve.org
SatelliteApplication · Redhat

CVE-2023-4320

HIGH · 7.5 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 6.13 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An arithmetic overflow flaw was found in Satellite when creating a new personal access token. This flaw allows an attacker who uses this arithmetic overflow to create personal access tokens that are valid indefinitely, resulting in damage to the system's integrity.

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 · moderate confidence

An arithmetic overflow vulnerability in Red Hat Satellite allows attackers to create personal access tokens that never expire. The overflow likely occurs in the token duration/expiration timestamp calculation, causing the expiration field to wrap around to zero or a very large value, resulting in perpetually valid tokens.

MitigationApply the relevant Red Hat Security Advisory (RHSA) for CVE-2023-4320 which patches the arithmetic overflow in token creation. Audit existing personal access tokens for unexpectedly long or indefinite expiration dates and revoke any suspicious tokens.

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
SatelliteApplication
Affected:< 6.13

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Red Hat Satellite version
    Run 'satellite-installer --version' or check /etc/foreman/version file, or query the API: GET /api/v2/about
    Affected if Version is lower than 6.13 (e.g., 6.12.x, 6.11.x, etc.)
  2. List personal access tokens via API
    Run: hammer token list --user <username> or GET /api/users/<user_id>/tokens to enumerate existing PATs
    Affected if Tokens exist with expiration date set to 0, NULL, or a date far in the future (e.g., year 2038 or later)
  3. Inspect token creation parameters
    Check /usr/share/foreman/config/settings.yml or API responses during token creation for max_token_lifetime or similar duration settings
    Affected if Token expiration defaults or max values are set to extremely large numbers or wrap around to 0
  4. Review audit logs for token creation
    Search Foreman/Katello logs (e.g., /var/log/foreman/production.log) for 'POST /api/users/*/tokens' or 'AccessToken create' events, look for expiration values
    Affected if Recent token creation events show expiration timestamps of 0, epoch start, or year 2038+

You are affected if running Red Hat Satellite version below 6.13 AND you have personal access tokens with expiration dates set to 0, NULL, or dates extending many years into the future.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.13 or later
Fixed in 6.13
Interim mitigation

Apply the relevant Red Hat Security Advisory (RHSA) for CVE-2023-4320 which patches the arithmetic overflow in token creation. Audit existing personal access tokens for unexpectedly long or indefinite expiration dates and revoke any suspicious tokens.

Recommended fix High confidence

Satellite 6.13 or later

  1. Review Red Hat Satellite 6.13 release notes for upgrade prerequisites and known issues
  2. Ensure adequate backup of current Satellite configuration and data
  3. Schedule maintenance window for upgrade execution
  4. Upgrade Satellite to version 6.13 or later using standard upgrade procedures
  5. Verify the upgrade completed successfully
  6. Review all existing personal access tokens and revoke any that are unexpectedly long-lived or unauthorized
  7. Confirm the arithmetic overflow is resolved by creating a new personal access token with a defined expiration
Caveat Review Satellite 6.13 release notes for any breaking changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Satellite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4320 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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