dbcve.org
SatelliteApplication · Redhat

CVE-2017-7514

MEDIUM · 5.4 CVSS v3.0 Published 2018-07-30
Fix available
A fix is available. Upgrade to 5.8.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 cross-site scripting (XSS) flaw was found in how the failed action entry is processed in Red Hat Satellite before version 5.8.0. A user able to specify a failed action could exploit this flaw to perform XSS attacks against other Satellite users.

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

A stored XSS vulnerability in Red Hat Satellite versions before 5.8.0 allows authenticated users who can specify failed actions to inject malicious JavaScript into the failed action entry. This script executes when other Satellite users view these entries, compromising their sessions or performing actions on their behalf.

MitigationUpgrade to Red Hat Satellite version 5.8.0 or later which contains the fix for proper sanitization of failed action entries.

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:< 5.8.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Identify Red Hat Satellite version
    Run 'satellite --version' or check /usr/share/foreman/version file, or look in the Satellite web UI under Admin > Settings > About
    Affected if Version is below 5.8.0
  2. Check for failed action entries in the database
    Query the Satellite database (typically PostgreSQL) for entries in the 'actions' or 'failed_actions' table using: SELECT * FROM actions WHERE status = 'failed' LIMIT 10;
    Affected if Any failed action entries exist in the system
  3. Verify user access to failed action views
    Check Satellite user roles and permissions for accessing action/failed action views. In the web UI, go to Admin > Users > click a user > check their roles and whether they have 'view_actions' permission
    Affected if Multiple users exist with permission to view failed action entries (not just the action creator)

You are affected if running Red Hat Satellite version below 5.8.0 AND there are failed action entries that can be viewed by users other than the one who created them.

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

Upgrade to Red Hat Satellite version 5.8.0 or later which contains the fix for proper sanitization of failed action entries.

Fix this in Satellite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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