SatelliteApplication · Redhat
CVE-2014-8168
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 · uneditedRed Hat Satellite 6 allows local users to access mongod and delete pulp_database.
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 confidenceRed Hat Satellite 6 contains a local privilege escalation vulnerability where local users can access the mongod (MongoDB) process and delete the pulp_database. This allows unauthorized local users to potentially cause data loss or service disruption by accessing the database daemon directly and removing critical application data.
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
= 6.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Red Hat Satellite versionCheck if the system is running Red Hat Satellite version 6.0 by querying the installed package version (e.g., rpm -q rhn-satellite or satellite-common)Affected if The installed version is exactly 6.0
-
Confirm mongod process is runningIdentify if the mongod process is currently running on the system (e.g., ps aux | grep mongod or checking for port 27017 listeners)Affected if mongod is running and exposed to local users
-
Check mongod binary permissionsInspect the file permissions on the mongod binary to determine if unprivileged users can execute or access it (e.g., ls -l $(which mongod) or locate mongod binary)Affected if mongod binary is readable or executable by world or group permissions
-
Inspect pulp_database directory permissionsExamine the file system permissions on the pulp_database directory and its contents to determine if local users have write or delete accessAffected if pulp_database directory is writable or accessible by unprivileged local users
-
Verify local user access to mongodTest whether a local unprivileged user can connect to the mongod process, execute commands, or access the pulp_database (e.g., check if mongod auth is disabled or if local socket is accessible)Affected if Unprivileged local users can directly interact with mongod or delete pulp_database contents
A system is affected if it runs Red Hat Satellite 6.0 with mongod accessible to local unprivileged users and pulp_database writable by non-privileged accounts.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict file system permissions on mongod and the pulp_database directories to prevent local user access. Configure SELinux policies to enforce isolation and ensure only privileged Satellite processes can interact with these resources.
Fix this in Satellite
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-8168 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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