Skip to content

Binary Planting Attack on Windows Platforms

Low
atodorov published GHSA-cx5c-xwcv-vhmq Jan 17, 2024

Package

creditcoin-node

Affected versions

None

Patched versions

None

Description

Summary

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 possible to replace these DLLs and execute arbitrary code. For more details on this type of binary planting attack please refer to this OWASP.org article.

Details

The DLLs loaded at startup on Windows are the following:

  1. iphlpapi.dll - Windows networking subsystem
  2. bcrypt.dll - Windows cryptographic primitives
  3. MSVCP140.dll - Part of Microsoft C++ Runtime library
  4. VCRUNTIME140.dll - Part of the visual studio runtime
  5. VCRUNTIME140_1.dll - More runtime stuff
  6. VCRUNTIME140.dll - runtime
  7. VCRUNTIME140_1.dll - runtime
  8. CRYPTBASE.DLL - Microsoft cryptographic API

Impact

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.

Credits

Originally disclosed by dobermann-pinscher at https://huntr.com/bounties/2effbbcb-47a7-426e-b022-900aa966367f/

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

CVE ID

CVE-2024-22410

Weaknesses

Credits