This vulnerability occurs when a value is stored in a variable, but that variable is never read or used in subsequent code, creating a 'dead store.'
A dead store happens when a variable is assigned a value, only to be immediately overwritten by another assignment or to fall out of scope without being referenced. This often indicates leftover code from a previous implementation or refactoring, but it can also be a subtle sign of a logic error—perhaps a critical calculation was meant to be used but was accidentally omitted. While these issues can seem minor, they clutter code, harm performance, and may mask deeper bugs. Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these flaws across your entire stack by identifying dead stores and using AI to suggest precise clean-up actions, turning security hygiene into an automated process.
Impact: Quality DegradationVaries by Context
This weakness could be an indication of a bug in the program or a deprecated variable that was not removed and is an indication of poor quality. This could lead to further bugs and the introduction of weaknesses.
c