dbcve.org
SatelliteApplication · Redhat

CVE-2019-3845

HIGH · 8.0 CVSS v3.1 Published 2019-04-11
Fix available
A fix is available. Upgrade to 6.2 or later.
See remediation →
82/100
Remediation priority · High
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 lack of access control was found in the message queues maintained by Satellite's QPID broker and used by katello-agent in versions before Satellite 6.2, Satellite 6.1 optional and Satellite Capsule 6.1. A malicious user authenticated to a host registered to Satellite (or Capsule) can use this flaw to access QMF methods to any host also registered to Satellite (or Capsule) and execute privileged commands.

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 lack of access control in the QPID broker message queues used by katello-agent allows an authenticated user on one registered host to access QMF methods on any other registered host, enabling execution of privileged commands. The vulnerability exists in Satellite versions before 6.2 and in Satellite 6.1 optional/Capsule 6.1.

MitigationUpgrade to Satellite 6.2 or later which implements proper access control on QPID message queues. For Satellite 6.1 deployments, apply the relevant security patch that restricts QMF method access to only the intended host.

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

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

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

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. Verify katello-agent is installed
    Check if the katello-agent package or service is present on the system. On RHEL-based systems, run 'rpm -q katello-agent' or check for the 'goferd' service which katello-agent depends on.
    Affected if katello-agent is installed and running on a host registered to a vulnerable Satellite server
  2. Confirm Satellite server version
    On the Satellite server or Capsule, check the version by running 'satellite-installer --version' or looking for the Satellite version file. Compare the installed version against the affected range of versions before 6.2.
    Affected if The Satellite or Capsule server version is lower than 6.2
  3. Identify QPID usage for agent communication
    Verify that katello-agent is configured to communicate with the Satellite server via QPID. Check katello-agent configuration files for QPID broker settings and confirm the QPID service is running.
    Affected if QPID is enabled and used for katello-agent to Satellite communication
  4. Confirm host registration status
    Determine if the system is registered to a Satellite server by checking subscription manager status or Foreman host facts. A host must be registered to a Satellite for the vulnerability to be exploitable.
    Affected if The system is registered to a Satellite server that is version 6.1 or earlier

If katello-agent is installed on a host registered to a Satellite server running a version before 6.2, and QPID is used for agent communication, the environment is affected by this access control bypass.

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 6.2 or later
Fixed in 6.2
Interim mitigation

Upgrade to Satellite 6.2 or later which implements proper access control on QPID message queues. For Satellite 6.1 deployments, apply the relevant security patch that restricts QMF method access to only the intended host.

Fix this in Satellite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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