HexBrain

U.S. Dept Of Defense · Report #3242830

Critical PII Data Exposure in ORDER_ERROR_LOG

Validstatus
highseverity
7upvotes
12 Jan 2026disclosed

How it was found

A critical security vulnerability has been identified in the application's error logging system where the ORDER_ERROR_LOG file contains complete database insertion statements that expose Personally Identifiable Information (PII) of customers in plain text format.

Root Cause

The application's error handling mechanism is logging full SQL INSERT statements when database operations fail. These statements contain complete customer records including sensitive personal information that should never be stored in log files.

What Data is ExposedThe logs contain complete customer records including: Full names Email addresses Phone numbers Home addresses Customer IDs Transaction amounts ....

simple of data

INSERT INTO dli.dli_customer_data VALUES (
                dli_customer_data_sequence.NEXTVAL,
                SYSDATE,
                ████████,
                ███,
                ██████████,
                ████,
                ██████,
                ██████,
                █████████,
                █████████,
                ███████,
                █████,
                ███,
                █████,
                ███,
                ████████,
                ████,
                ██████████,
                'Surface',
                '14.00',
                '15.4',
                '17.5')

███████ ████

Impact

Unintended Data Persistence: Customer PII persists in log files beyond intended retention periods Expanded Attack Surface: Log files become high-value targets containing concentrated PII Compliance Violations: Direct violation of data minimization principles required by privacy regulations Audit Trail Contamination: Security logs contain sensitive data that complicates forensic analysis

System Host(s)

dlielc.edu

Affected Product(s) and Version(s)

CVE Numbers

Steps to Reproduce

  1. Access the ORDER_ERROR_LOG file ███████
  2. Review the contents for database INSERT statements. INSERT INTO dli.dli_customer_data VALUES (
  3. Observe exposed customer data
  INSERT INTO dli.dli_customer_data VALUES (
                dli_customer_data_sequence.NEXTVAL,
                SYSDATE,
                █████████,
                ██████,
                ███████,
                'FPO',
                'AP',
                ██████████,
                ████████,
                ███,
                ██████████,
                'FPO',
                'AP',
                ███████,
                ████████,
                █████,
                ██████,
                ██████,
                'Air',
                '480.00',
                ████████,
                '600')

Suggested Mitigation/Remediation Actions

Implement data sanitization in error logging to prevent PII exposure.

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original