dbcve.org
SatelliteApplication · Redhat

CVE-2021-3414

HIGH · 8.1 CVSS v3.1 Published 2022-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 flaw was found in satellite. When giving granular permission related to the organization, other permissions allowing a user to view and manage other organizations are also granted. The highest threat from this vulnerability is to data confidentiality.

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 confidence

A flaw in Red Hat Satellite allows granular organization permissions to inadvertently grant broader permissions to view and manage other organizations, enabling unauthorized cross-organization data access.

MitigationReview and restrict existing user permission assignments to ensure only intended organization-level access is granted until an official patch is applied.

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

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Red Hat Satellite version
    Run 'satellite-installer --version' or check /etc/foreman/version file to determine if the installed version is 6.7
    Affected if Installed version equals 6.7 exactly
  2. Identify users with multi-organization access
    Use Satellite API or web UI to list all users assigned to roles that span multiple organizations. Look for users with roles containing 'organization' in the name
    Affected if Any user account has permissions assigned across more than one organization
  3. Review organization-scoped roles
    Examine role definitions in Satellite under Administer > Users > Roles. Check for roles that have both organization-specific and global permissions enabled simultaneously
    Affected if A role grants view or manage permissions to organizations beyond the user's primary organization
  4. Check cross-organization data access permissions
    Inspect role permissions for 'view_organizations', 'edit_organizations', or similar. Verify whether any role with these permissions is assigned to users in an organization different from what the permission scope would imply
    Affected if Users can view or manage organizations they are not explicitly assigned to
  5. Audit user role assignments
    List all user-role associations and compare each user's organization membership against their assigned role permissions. Flag any user whose role permissions extend beyond their organization membership
    Affected if A user's assigned role provides access to organizations where that user is not a member

If Satellite 6.7 is installed AND any users have organization-spanning role permissions that exceed their actual organization membership, the environment is affected by this vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and restrict existing user permission assignments to ensure only intended organization-level access is granted until an official patch is applied.

Recommended fix Moderate confidence

Red Hat Satellite 6.7.x (latest update) or upgrade to Satellite 6.8+

  1. 1. Back up the current Satellite 6.7 configuration and databases
  2. 2. Review Red Hat Satellite 6.7 release notes and errata for available updates
  3. 3. Run 'yum update' or use Red Hat Satellite's update mechanism to apply the latest patches
  4. 4. Verify the permission fix is included in the applied update
  5. 5. After update, test the granular organization permissions to confirm users only receive explicitly granted permissions
  6. 6. Verify users cannot view or manage organizations outside their granted scope
Caveat Review release notes for potential breaking changes between 6.7 and subsequent versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Satellite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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