Security Resilience

CVE-2024-10026

Crypto Weakness in Google Gvisor ≤ 20231030.0

Public PoCCrypto Weakness
Published
30 January 2025
Modified
31 July 2025
Patch / advisory
View advisory
CVSS Score v4 6.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0022 12th percentile
Risk Priority 38 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-10026 is a medium-severity Use of Weak Hash (CWE-328) vulnerability in Google Gvisor. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP address and a per-boot identifier that could aid in tracking of a device in certain circumstances.

CWE(s)
CWE-328CWE-339CWE-326CWE-335

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-2713Same product: Google Gvisor
CVE-2023-7258Same product: Google Gvisor
CVE-2024-10603Same product: Google Gvisor
CVE-2026-10999Same vendor: Google
CVE-2024-8636Same vendor: Google
CVE-2024-8198Same vendor: Google
CVE-2024-7534Same vendor: Google
CVE-2024-34740Same vendor: Google
CVE-2026-0161Same vendor: Google
CVE-2024-43091Same vendor: Google

Affected Assets

google
gvisor
≤ 20231030.0 · 20231106.0 — 20231204.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.2.3
  • V7.2.3
  • V6.5.2
  • V11.5.1

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Mandating approved cryptographic algorithms and strengths directly stops selection of weak hash functions for integrity or other uses.

SC-12 Cryptographic Key Establishment and Management good match

Cryptographic key establishment and management practices mandate sufficient entropy sources when seeding PRNGs used for keys.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles applied during design require cryptographically sound PRNG seeding with adequate entropy.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 partial match
blocks

Proper data-at-rest integrity protection requires strong cryptographic hashes, directly blocking weak-hash usage.

PR.DS-02 partial match
blocks

Data-in-transit integrity likewise depends on strong hashes, so the control prevents the weakness while the weakness only partially satisfies the outcome.

PR.PS-06 partial match
blocks

Secure-SDLC requirements explicitly forbid weak cryptographic algorithms, fully preventing CWE-328 while covering only one aspect of development practice.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.31 Legal, statutory, regulatory and contractual requirements partial match
removes
A.5.36 Compliance with policies, rules and standards for information security partial match
removes
A.8.19 Installation of software on operational systems partial match
removes
A.8.24 Use of cryptography partial match
prevents

A.8.24's policy, algorithm selection (b,f), and key management directly require strong hashes meeting security expectations, preventing weak-hash use in most approved cryptographic contexts, but leaves a bounded remainder for non-crypto uses of hashing (e.g. data structures, non-security checksums) where the clause has no mandate.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including those that could call for strong hashing via 8.24) be identified during development or acquisition; it does not itself mandate, enforce or implement any specific algorithm or protection that stops a weak hash from being exploitable.

A.8.27 Secure system architecture and engineering principles partial match
removes

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248563 The OL 8 SSH server must be configured to use strong entropy. blocks CWE-335
RHEL 8 (1 rule)
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. blocks CWE-335
Windows 10 (1 rule)
  • V-220937 The system must be configured to prevent the storage of the LAN Manager hash of passwords. blocks CWE-328
Windows Server 2016 (1 rule)
  • V-225053 Windows Server 2016 must be configured to prevent the storage of the LAN Manager hash of passwords. blocks CWE-328
Windows Server 2019 (1 rule)
  • V-205654 Windows Server 2019 must be configured to prevent the storage of the LAN Manager hash of passwords. blocks CWE-328

References