Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2021-3413

Satellite: Azure compute resource secret_key leak to authenticated users

Overview

Published
8 Apr 2021
Modified
17 Jun 2026
Medium CVE
1 Registry packages
14 OS packages
1 Linux distributions
Yes Fix available

Description

A flaw was found in Red Hat Satellite in tfm-rubygem-foreman_azure_rm in versions before 2.2.0. A credential leak was identified which will expose Azure Resource Manager's secret key through JSON of the API output. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Source: OX vulnerability database

Severity

6.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Weakness: CWE-200

Affected packages · 1

Packages affected by CVE-2021-3413
EcosystemPackageVulnerableFixed in
RubyGems foreman_azure_rm — 2.2.0

Open a package to see all its vulnerabilities.

Operating systems · 12 fixes

Red Hat 1 release · 12 packages

fixed 12
python3-ecdsa tfm-rubygem-nokogiri python3-urllib3 tfm-rubygem-activerecord-session-store python3-django foreman +6
Red Hat fixes for CVE-2021-3413
ReleasePackageFixed inAdvisory
7 python3-ecdsa 0:0.13.3-2.el7pc RHSA-2021:4702
7 tfm-rubygem-nokogiri 0:1.11.3-2.el7sat RHSA-2021:4702
7 python3-urllib3 0:1.26.5-1.el7pc RHSA-2021:4702
7 tfm-rubygem-activerecord-session-store 0:2.0.0-1.el7sat RHSA-2021:4702
7 python3-django 0:2.2.24-1.el7pc RHSA-2021:4702
7 foreman 0:2.5.2.17-2.el7sat RHSA-2021:4702

6 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.