CVE-2019-3845
Public on
Last Modified:
Insights vulnerability analysis
Description
A lack of access control was found in the message queues maintained by Satellite's QPID broker and used by katello-agent. 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.
Statement
On Red Hat Satellite 6.5, the Satellite 6.5 GA release includes a version of katello-installer-base that provides the fixes for this issue.
Mitigation
On Satellite Server follow the instructions below:
* Modify /etc/qpid/qpidd.conf to add this line:
acl-file=qpid_acls.acl
* Create a new file: /var/lib/qpidd/.qpidd/qpid_acls.acl with content:
acl allow katello_agent@QPID create queue
acl allow katello_agent@QPID consume queue
acl allow katello_agent@QPID access exchange
acl allow katello_agent@QPID access queue
acl allow katello_agent@QPID publish exchange routingkey=pulp.task
acl allow katello_agent@QPID publish exchange name=qmf.default.direct
acl allow katello_agent@QPID access method name=create
acl deny-log katello_agent@QPID access method name=*
acl deny-log katello_agent@QPID all all
# allow anything else
acl allow all all
* As root, execute the command:
# systemctl restart qpidd
* In /etc/qpid-dispatch/qdrouterd.conf modify the connector:
connector {
name: broker
host: localhost
port: 5671
sasl-mechanisms: PLAIN
sasl-username: katello_agent
sasl-password: katello_agent
role: route-container
ssl-profile: client
idle-timeout-seconds: 0
}
* As root, execute the command:
# systemctl restart qdrouterd
These ACLs will prevent clients to redirect or move messages to various queues which is the nature of the CVE.
All other behavior will be unchanged (acl allow all all) which is the current baseline.
Additional information
- Bugzilla 1684275: katello-installer-base: QMF methods exposed to goferd via qdrouterd
- CWE-284: Improper Access Control
- FAQ: Frequently asked questions about CVE-2019-3845
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
| Red Hat | NVD | |
|---|---|---|
CVSS v3 Base Score | 8 | 8 |
Attack Vector | Adjacent Network | Adjacent Network |
Attack Complexity | Low | Low |
Privileges Required | Low | Low |
User Interaction | None | None |
Scope | Unchanged | Unchanged |
Confidentiality Impact | High | High |
Integrity Impact | High | High |
Availability Impact | High | High |
CVSS v3 Vector
Red Hat: CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
Acknowledgements
This issue was discovered by Pavel Moravec (Red Hat).
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
