SatelliteApplication · Redhat
CVE-2014-8183
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 · uneditedIt was found that foreman, versions 1.x.x before 1.15.6, in Satellite 6 did not properly enforce access controls on certain resources. An attacker with access to the API and knowledge of the resource name can access resources in other organizations.
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 confidenceThis is an broken access control vulnerability in Foreman's API (versions 1.x.x before 1.15.6 in Red Hat Satellite 6). The application fails to properly enforce organization-based access restrictions, allowing an authenticated API user who knows a resource's name to access that resource even when it belongs to a different organization, effectively bypassing multi-tenant isolation.
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.0>= 1.0, < 1.15.6CVSS 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
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
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.
-
Check Foreman versionQuery the Foreman API or web interface to retrieve the installed version number. On the CLI, you can often run 'foreman --version' or check /usr/share/foreman/Gemfile in some installations. Compare your version against the affected range: versions 1.0 through 1.15.5 (anything below 1.15.6).Affected if Your installed Foreman version is 1.x where x is less than 6, or specifically any version below 1.15.6.
-
Confirm Satellite 6.0 deploymentIdentify if your environment is running Red Hat Satellite version 6.0, as this bundles the affected Foreman version.Affected if Your environment is Red Hat Satellite 6.0.
-
Verify API access is enabledCheck if the Foreman API service is accessible. This typically involves confirming the API port (often 443 or 8443) is listening and that API endpoints respond to requests.Affected if The Foreman API is exposed and accessible in your environment.
-
Confirm multi-organization feature is activeExamine whether your Foreman deployment has multiple organizations configured. Check the Organizations settings in the Foreman web UI or via API call to /api/organizations to list defined organizations.Affected if More than one organization is defined in your Foreman instance.
You are affected if your Foreman version is 1.x before 1.15.6 (or you run Satellite 6.0) AND you have the API enabled with multiple organizations configured, allowing an authenticated API user to potentially access resources outside their organization.
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 data1.15.6
Upgrade Foreman to version 1.15.6 or later to obtain the patch that enforces proper organization-based access controls on API resources.
Fix this in Satellite
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8183 — 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-8183 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