dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-8553

MEDIUM · 6.3 CVSS v3.1 Published 2024-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability was found in Foreman's loader macros introduced with report templates. These macros may allow an authenticated user with permissions to view and create templates to read any field from Foreman's database. By using specific strings in the loader macros, users can bypass permissions and access sensitive information.

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

Foreman's loader macros in report templates contain a permission bypass vulnerability allowing authenticated users with view/create template permissions to read arbitrary database fields by injecting specific strings into loader macros, effectively bypassing standard role-based access controls.

MitigationRestrict template permissions to only trusted users, audit existing report templates for malicious loader macro usage, and apply vendor patches to properly validate and sanitize loader macro inputs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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. Identify Foreman installation and version
    Run 'foreman --version' from the Foreman server, or check /usr/share/foreman/lib/foreman/version.rb, or look at the web UI footer for the version number
    Affected if The installed version falls within the affected range and the product is Foreman with report template functionality enabled
  2. Verify report templates are in use
    Check if report templates exist by querying the API endpoint /api/report_templates or listing templates in the Foreman web UI under Monitor > Report Templates
    Affected if Report templates are created and accessible, indicating the vulnerable feature is present
  3. Examine template permission assignments
    Navigate to Administer > Users > (select user) > Template or use hammer CLI: hammer user template-permissions list --user-id <id> to see which users have view/create permissions on report templates
    Affected if Users other than administrators have view or create permissions assigned to report templates, creating the condition for the bypass
  4. Check for loader macro usage in templates
    Review existing report templates by exporting them via hammer report-template dump --id <template_id> or via the UI, looking for syntax containing loader macros such as load_*, Kernel(). etc.
    Affected if Report templates contain loader macros that could be exploited to access arbitrary database fields
  5. Audit role-based access control settings
    Examine the roles assigned to non-admin users with template permissions using Administer > Roles in the web UI or hammer role list and hammer role filters, verify whether these roles restrict access to sensitive database tables
    Affected if Non-administrator users with template permissions exist and those roles do not explicitly deny access to sensitive database fields, meaning the permission bypass is theoretically exploitable

A user is affected if they run a Foreman version with this vulnerability and have non-administrator users granted view or create permissions on report templates containing loader macros.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict template permissions to only trusted users, audit existing report templates for malicious loader macro usage, and apply vendor patches to properly validate and sanitize loader macro inputs.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8553 — 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-2024-8553 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