dbcve.org
SatelliteApplication · Redhat

CVE-2016-2104

MEDIUM · 6.1 CVSS v3.0 Published 2017-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Multiple cross-site scripting (XSS) vulnerabilities in Red Hat Satellite 5 allow remote attackers to inject arbitrary web script or HTML via (1) the label parameter to admin/BunchDetail.do; (2) the package_name, (3) search_subscribed_channels, or (4) channel_filter parameter to software/packages/NameOverview.do; or unspecified vectors related to (5) <input:hidden> or (6) <bean:message> tags.

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

Red Hat Satellite 5 contains multiple reflected cross-site scripting (XSS) vulnerabilities where user-supplied input in the label parameter (admin/BunchDetail.do), package_name, search_subscribed_channels, and channel_filter parameters (software/packages/NameOverview.do), as well as unspecified vectors involving <input:hidden> and <bean:message> tags, is not properly sanitized before being rendered in the response.

MitigationImplement robust input validation and output encoding for all user-supplied parameters across the affected endpoints. Apply context-aware escaping before rendering any user input in HTML/JavaScript contexts.

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.7

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

CVSS:3.0/AV:N/AC:L/PR:N/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
    Check the installed version of Red Hat Satellite (for example, by examining the product version in the UI footer, /etc/redhat-release, or using the satellite version command if available)
    Affected if The installed version is exactly 5.7 (the only affected version listed)
  2. Confirm affected endpoint admin/BunchDetail.do is accessible
    Verify the web application path /admin/BunchDetail.do exists and is reachable in the Satellite installation
    Affected if This endpoint exists and accepts user input through the 'label' parameter without sanitization
  3. Confirm affected endpoint software/packages/NameOverview.do is accessible
    Verify the web application path /software/packages/NameOverview.do exists and is reachable
    Affected if This endpoint exists and accepts user input through package_name, search_subscribed_channels, or channel_filter parameters without sanitization
  4. Check for XSS-prone tag usage
    Inspect web application response handling for <input:hidden> and <bean:message> tag usage to determine if user-supplied values are reflected without output encoding
    Affected if These tags are used to render user input without proper context-aware escaping

A user is affected if they are running Red Hat Satellite version 5.7 AND have the vulnerable endpoints (admin/BunchDetail.do or software/packages/NameOverview.do) accessible with user input reflected in the response without sanitization.

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

Implement robust input validation and output encoding for all user-supplied parameters across the affected endpoints. Apply context-aware escaping before rendering any user input in HTML/JavaScript contexts.

Fix this in Satellite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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