Security Resilience

CVE-2024-22410

LPE in Gluwa Creditcoin

Published
17 January 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 3.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0022 11th percentile
Risk Priority 28 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-22410 is a low-severity Untrusted Search Path (CWE-426) vulnerability in Gluwa Creditcoin. Its CVSS base score is 3.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception by Unquoted Path (T1574.009); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Creditcoin is a network that enables cross-blockchain credit transactions. The Windows binary of the Creditcoin node loads a suite of DLLs provided by Microsoft at startup. If a malicious user has access to overwrite the program files directory it is…

more

possible to replace these DLLs and execute arbitrary code. It is the view of the blockchain development team that the threat posed by a hypothetical binary planting attack is minimal and represents a low-security risk. The vulnerable DLL files are from the Windows networking subsystem, the Visual C++ runtime, and low-level cryptographic primitives. Collectively these dependencies are required for a large ecosystem of applications, ranging from enterprise-level security applications to game engines, and don’t represent a fundamental lack of security or oversight in the design and implementation of Creditcoin. The blockchain team takes the stance that running Creditcoin on Windows is officially unsupported and at best should be thought of as experimental.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1574.009 Path Interception by Unquoted Path Stealth
Adversaries may execute their own malicious payloads by hijacking vulnerable file path references.
T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
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.
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-24789Same product: Microsoft Windows
CVE-2026-48275Same product: Microsoft Windows
CVE-2023-34145Same product: Microsoft Windows
CVE-2024-47422Same product: Microsoft Windows
CVE-2026-23512Same product: Microsoft Windows
CVE-2026-63093Same product: Microsoft Windows
CVE-2026-21333Same product: Microsoft Windows
CVE-2024-36071Same product: Microsoft Windows
CVE-2023-34144Same product: Microsoft Windows
CVE-2026-27290Same product: Microsoft Windows

Affected Assets

gluwa
creditcoin
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Secure baseline settings can enforce absolute, organization-controlled paths for critical resources.

Least-functionality configuration can prohibit unapproved directories or executables from being reachable via search paths.

Engineering principles such as trusted paths, complete mediation, and least privilege directly require hard-coded or validated search paths instead of external ones.

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

Hardened configuration baselines can enforce safe search paths and restrict environment variables that enable the weakness.

PR.PS-05 partial match
blocks

Preventing execution of unauthorized code directly blocks the malicious binaries that an untrusted search path would load.

PR.PS-06 partial match
blocks

Secure development practices include avoiding or sanitizing externally influenced search paths in application code.

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.

removes
removes
removes
removes
removes

References