When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.

From PostgreSQL 9.x Security Technical Implementation Guide

Part of SRG-APP-000447-DB-000393

Associated with: CCI-002754

SV-87559r2_rule When invalid inputs are received, PostgreSQL must behave in a predictable and documented manner that reflects organizational and system objectives.

Vulnerability discussion

A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state.The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input.

Check content

As the database administrator (shown here as "postgres"), make a small SQL syntax error in psql by running the following:  $ sudo su - postgres  $ psql -c "CREAT TABLEincorrect_syntax(id INT)"  ERROR: syntax error at or near "CREAT"  Note: The following instructions use the PGVER environment variable. See supplementary content APPENDIX-H for instructions on configuring PGVER. Now, as the database administrator (shown here as "postgres"), verify the syntax error was logged (change the log file name and part to suit the circumstances):  $ sudo su - postgres  $ cat ~/${PGVER?}/data/pg_log/postgresql-Wed.log  2016-03-30 16:18:10.772 EDT postgres postgres 5706bb87.90dERROR: syntax error at or near "CREAT" at character 1  2016-03-30 16:18:10.772 EDT postgres postgres 5706bb87.90dSTATEMENT: CREAT TABLE incorrect_syntax(id INT);  Review system documentation to determine how input errors from application to PostgreSQL are to be handled in general and if any special handling is defined for specific circumstances.  If it does not implement the documented behavior, this is a finding.

Fix text

Enable logging. To ensure that logging is enabled, review supplementary content APPENDIX-C for instructions on enabling logging. All errors and denials are logged if logging is enabled.

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