CWE-540 Inclusion of Sensitive Information in Source Code

The product (such as a web server or repository) provides access to source code is not intended to be accessible to users but contains sensitive information.

• Confidentiality: Read Application Data, Varies by Context — Obtaining source code on a system allows an attacker to understand the logic of the script and extract extremely useful information such as code bugs or logins and passwords.

• [Architecture and Design, System Configuration] Recommendations include removing the script from the web server and moving it to a location not accessible from the Internet.

• 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.)

• CVE-2022-25512: Server for Team Awareness Kit (TAK) application includes sensitive tokens in the JavaScript source code. • CVE-2022-24867: The LDAP password might be visible in the html code of a rendered page in an IT Asset Management tool. • CVE-2007-6197: Version numbers and internal hostnames leaked in HTML comments.