Skip to content
OpenAdvisories

Weakness (CWE)

CWE-547: Use of Hard-coded, Security-relevant Constants

Base Draft

The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change.

How to prevent it (1 mitigation)
  1. Implementation

    Avoid using hard-coded constants. Configuration files offer a more flexible solution.

Source: MITRE CWE-547

2 results · Clear filters · Feed

  • Low 2.5

    NVIDIA NvContainer service for Windows contains a vulnerability in its usage of OpenSSL, where an attacker could exploi…

  • Low 3.9

    Local Git clone may hardlink arbitrary user-readable files into the new repository's "objects/" directory

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the …