LiveActive security incident?Get immediate response
CVE Record

CVE-2021-36778: Exposure of repository credentials to external third-party sources

A Incorrect Authorization vulnerability in SUSE Rancher allows administrators of third-party repositories to gather credentials that are sent to their servers. This issue affects: SUSE Rancher Rancher versions prior to 2.5.12; Rancher versions prior to 2.6.3.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Rancher could expose repository credentials to administrators of third-party repositories that receive those credentials. The business risk is credential leakage through trusted integrations, not a proven public takeover. The sources identify affected Rancher versions before 2.5.12 and before 2.6.3.

Executive priority

Prioritize remediation for Rancher environments connected to third-party repositories or using long-lived shared credentials. The issue is high severity because it can expose credentials, but current provided sources do not prove active exploitation.

Technical view

CVE-2021-36778 is an incorrect authorization issue in SUSE Rancher. Third-party repository administrators may gather credentials sent to their servers. The CVSS 3.1 score is 7.3 high, with low attack complexity and network attack vector. Source detail is limited beyond affected versions and the authorization failure category.

Likely exposure

Exposure is most likely where SUSE Rancher versions earlier than 2.5.12 or 2.6.3 use third-party repositories with credentials. Systems without third-party repository integrations may have lower practical exposure, but the source bundle does not define all prerequisite conditions.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The plausible threat actor is a third-party repository administrator who can receive credential-bearing requests. Treat this as credential exposure risk requiring review of repository trust and credential scope.

Researcher notes

The evidence names CWE-863 and affected Rancher versions only. No CPEs, exploit details, or comprehensive mitigation notes are included in the bundle. Avoid assuming broader SUSE products or Kubernetes components are affected without vendor confirmation.

Mitigation direction

  • Upgrade Rancher to 2.5.12, 2.6.3, or a later vendor-supported release.
  • Review SUSE Rancher advisory guidance before choosing an upgrade path.
  • Rotate credentials used with third-party repositories on affected Rancher instances.
  • Remove or restrict untrusted third-party repository integrations.
  • Scope repository credentials to least privilege where possible.

Validation and detection

  • Inventory all Rancher instances and record exact versions.
  • Identify configured third-party repositories and associated credentials.
  • Confirm affected instances are upgraded beyond the listed vulnerable versions.
  • Review repository and Rancher audit logs for unexpected credential use.
  • Verify rotated credentials no longer authenticate from old trust paths.
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-863: 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-2021-36778 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2021-36778Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SUSERancherRancherListed
SUSERancherRancherListed
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

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