LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8183: It was found that foreman, versions 1.x.x before 1.15.6, in Satellite 6 did not properly enforce access con...

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

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2014-8183 is an authorization failure in Foreman 1.x before 1.15.6 as used with Satellite 6. A user who can access the API and knows a resource name may access resources belonging to other organizations. The main business risk is cross-tenant data exposure or unauthorized changes inside shared management environments.

Executive priority

Treat this as high priority for shared Satellite or Foreman environments because it undermines organizational separation. Prioritize internet-reachable, broadly accessible, or multi-tenant management systems first, then complete fleet-wide version and access reviews.

Technical view

The issue is CWE-284 improper access control. The CVSS 3.0 vector is network exploitable, low complexity, low privileges required, no user interaction, and changed scope, with low confidentiality, integrity, and availability impact. Public sources identify Foreman 1.x before 1.15.6 as affected.

Likely exposure

Exposure is most likely where Foreman 1.x before 1.15.6 or Satellite 6 deployments expose the API to multiple users, teams, or organizations. Single-tenant or tightly restricted API deployments have lower practical exposure, but still need version verification.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires authenticated API access plus knowledge of a resource name, so insider, compromised account, or overly broad API access scenarios matter most.

Researcher notes

Public detail is limited. The key confirmed conditions are authenticated API access, knowledge of resource name, and affected Foreman 1.x before 1.15.6 in Satellite 6 context. Avoid assuming unauthenticated access or public exploit availability without additional evidence.

Mitigation direction

  • Upgrade Foreman to 1.15.6 or later where applicable.
  • Check Red Hat Satellite 6 vendor guidance and errata for fixed packages.
  • Restrict Foreman API access to trusted users and networks.
  • Review organization boundaries, roles, and resource permissions.
  • Monitor API activity for cross-organization access patterns.

Validation and detection

  • Inventory Foreman and Satellite 6 versions across environments.
  • Confirm whether any instance runs Foreman 1.x before 1.15.6.
  • Review API-enabled accounts and their organization memberships.
  • Validate users cannot access other organizations' resources by name.
  • Check logs for unusual API reads or changes across organizations.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-8183 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L3.13.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.4High
CVSS 3.0 vector shape for CVE-2014-8183Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
theforemanforeman1.x.x before 1.15.6Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.