How to fix: Perl CGI Software Error Page Exposed
A classic Perl CGI 'Software error:' page with a script path and line number was found in the response.
Why it matters
The error page discloses the full server-side script path and the exact line that failed, useful reconnaissance for an attacker targeting a legacy CGI application.
CGI.pm and similar legacy Perl CGI libraries print 'Software error:' followed by the die() message and 'at <script>.pl line N' directly into the HTTP response by default when an uncaught error occurs.
How to fix it
- 1Wrap the script body in an eval block and return a generic error page on failure.
- 2Use CGI::Carp's fatalsToBrowser only in development, never in production.
- 3Log the real error server-side instead of rendering it to the client.
Code examples
Generic error handling in Perl CGI
eval {
# request handling logic
};
if ($@) {
warn "Internal error: $@";
print "Status: 500 Internal Server Error\r\n\r\n";
print "An unexpected error occurred.";
}References
Detected automatically by VulnRadar. The check id is perl-cgi-error-exposed, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is Perl CGI Software Error Page Exposed?
- VulnRadar rates this medium severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id perl-cgi-error-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Perl CGI Software Error Page Exposed map to?
- It maps to CWE-209. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.