CWE-540: Inclusion of Sensitive Information in Source Code
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
How it's found
Inclusion of Sensitive Information in Source Code is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
There are situations where it is critical to remove source code from an area or server. For example, obtaining Perl 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.
Consequences
- Read Application Data
Mitigations
- Architecture and Design/System Configuration: Recommendations include removing this script from the web server and moving it to a location not accessible from the Internet.
How TurboPentest tests for this (white-box)
This weakness (Inclusion of Sensitive Information in Source Code) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 1 rule for it, flagging the issue directly in your source code as part of the pentest.
Frequently asked questions
What is CWE-540?
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
How do you find Inclusion of Sensitive Information in Source Code?
Inclusion of Sensitive Information in Source Code is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.
What is the impact of CWE-540?
Read Application Data
Does TurboPentest test for Inclusion of Sensitive Information in Source Code?
This weakness (Inclusion of Sensitive Information in Source Code) is caught by white-box static analysis when you connect a GitHub repo: IntegSec's Opengrep SAST rule pack carries 1 rule for it, flagging the issue directly in your source code as part of the pentest.
Related CWEs
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest