CWEweakness
CWE-1102 Reliance on Machine-Dependent Data Representation
- Abstraction
- Base
- Structure
- Simple
- Status
- Incomplete
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
The code uses a data representation that relies on low-level
data representation or constructs that may vary across different processors,
physical machines, OSes, or other physical components.
Common consequences
• Other: Reduce Maintainability — This issue makes it more difficult to maintain and/or port the product, which indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities. It also might make it easier to introduce vulnerabilities.
Detection methods
• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Observed examples
• CVE-2025-47153: Chain: build process for JavaScript runtime environment can have inconsistent sizes for off_t (CWE-1102), allowing out-of-bounds access / segmentation fault (CWE-119)
Related
Observed example · CVE (1)
- CVE-2025-47153 Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through… vulnerability
Child of · CWE (1)
- CWE-758 Reliance on Undefined, Unspecified, or Implementation-Defined Behavior weakness
Peer of · CWE (1)
- CWE-1105 Insufficient Encapsulation of Machine-Dependent Functionality weakness
Referenced by CVE · weakness (1)
- CVE-2025-47153 Certain build processes for libuv and Node.js for 32-bit systems, such as for the nodejs binary package through… vulnerability