The application must reveal error messages only to the ISSO, ISSM, or SA.

From Application Security and Development Security Technical Implementation Guide

Part of SRG-APP-000267

Associated with: CCI-001314

SV-84897r1_rule The application must reveal error messages only to the ISSO, ISSM, or SA.

Vulnerability discussion

Only authorized personnel should be aware of errors and the details of the errors. Error messages are an indicator of an organization's operational state or can identify application components. Additionally, Personally Identifiable Information (PII) and operational information must not be revealed through error messages to unauthorized personnel or their designated representatives.The structure and content of error messages must be carefully considered by the organization and development team. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.Error messages should not include variable names, variable types, SQL strings, or source code. Errors that contain field names from the screen and a description of what should be in the field should not be considered a finding.

Check content

Review the application documentation and interview the application administrator for details regarding how the application displays error messages. Authenticate to the application as a non-privileged user and attempt to execute functionality that will generate error messages. Review the error messages displayed to ensure no sensitive information is provided to end users. Authenticate as a privileged user and repeat tests. If error messages are designed to provide users with just enough detail to pass along to support staff in order to aid in troubleshooting such as date, time or other generic information, this is not a finding. If detailed error messages are provided to privileged users, this is not a finding. If variable names, SQL strings, system path information, or source or program code are displayed in error messages sent to non-privileged users, this is a finding.

Fix text

Configure the server to only send error messages containing system information or sensitive data to privileged users. Use generic error messages for non-privileged users.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer