Cyber 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 13th percentile
Risk Priority 38 floored blend · peak EPSS

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 Brute Force (T1110); ranked at the 13th 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

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
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 →
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
T1555 Credentials from Password Stores Credential Access
Adversaries may search for common password storage locations to obtain user credentials.
attack.mitre.org →
T1555.005 Password Managers Credential Access
Adversaries may acquire user credentials from third-party password managers.
attack.mitre.org →
T1606 Forge Web Credentials Credential Access
Adversaries may forge credential materials that can be used to gain access to web applications or Internet services.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-10603Same product: Google Gvisor
CVE-2023-7258Same product: Google Gvisor
CVE-2025-2713Same product: Google Gvisor
CVE-2023-21109Same vendor: Google
CVE-2025-45769Same vendor: Google
CVE-2023-40093Same vendor: Google
CVE-2024-34721Same vendor: Google
CVE-2025-0093Same vendor: Google
CVE-2023-20923Same vendor: Google
CVE-2024-0019Same 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)
  • 21 hardening rules · 9 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.2.3
  • V7.2.3
  • V11.4.2
  • V14.1.2

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.PS-06 full match
prevents

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

PR.DS-01 mostly match
prevents

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

PR.DS-02 mostly match
prevents

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-01 partial match
prevents

Hardened baselines can enforce minimum cryptographic algorithm and key-length settings.

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.8.24 Use of cryptography mostly match
prevents

Mandates use of approved cryptographic algorithms, directly preventing weak-hash selection.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect weak-hash usage but does not prescribe algorithm choice.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong hashing, but the control is broader.

A.8.28 Secure coding partial match
prevents

Requires secure coding standards that forbid weak hash functions in source code.

A.8.5 Secure authentication none match
none

Strong authentication mechanisms rely on unpredictable random values, indirectly requiring proper PRNG seeding.

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` (authoritative 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. prevents CWE-335
Oracle Linux 9 (1 rule)
  • V-271756 OL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. prevents CWE-326
RHEL 8 (2 rules)
  • V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. prevents CWE-326
  • V-230253 RHEL 8 must ensure the SSH server uses strong entropy. prevents CWE-335
RHEL 9 (1 rule)
  • V-257879 RHEL 9 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. prevents CWE-326
Windows 10 (1 rule)
  • V-220937 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-328
Windows 11 (1 rule)
  • V-253461 The system must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-328
Windows Server 2016 (2 rules)
  • V-225053 Windows Server 2016 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-328
  • V-224843 Systems requiring data at rest protections must employ cryptographic mechanisms to prevent unauthorized disclosure and modification of the information at rest. prevents CWE-326
Windows Server 2019 (1 rule)
  • V-205654 Windows Server 2019 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-328
Windows Server 2022 (1 rule)
  • V-254474 Windows Server 2022 must be configured to prevent the storage of the LAN Manager hash of passwords. prevents CWE-328

References