Omission of Security-relevant Information
This vulnerability occurs when an application fails to capture or present crucial security-related details, such as the origin of a request or the specifics of a security event. Without this information, developers and security teams cannot effectively trace attacks or validate whether an operation is legitimate.
When security-relevant information is omitted, it creates a blind spot in your application's defense. Attackers can exploit this gap to launch attacks without leaving an audit trail, making it nearly impossible to perform forensic analysis, understand the attack vector, or attribute malicious activity. This lack of visibility undermines incident response and allows threats to persist undetected. To prevent this, ensure your application logs and displays key security events with sufficient context. This includes timestamps, source IP addresses, user identifiers, affected resources, and the nature of the action performed. Implementing structured logging and real-time monitoring dashboards turns this data into actionable intelligence, helping your team quickly identify, investigate, and mitigate security incidents.
Impact: Hide Activities
The source of an attack will be difficult or impossible to determine. This can allow attacks to the system to continue without notice.
ID : DX-174
This code logs suspicious multiple login attempts.Code Example:
phpID : DX-175
This code prints the contents of a file if a user has permission.Code Example:
php//resolve file if its a symbolic link* if(is_link($filename)){ ``` $realFile = readlink($filename); } if(fileowner($realFile) == $user){ echo file_get_contents($realFile); return; } else{ echo 'Access denied'; writeLog($user . ' attempted to access the file '. $filename . ' on '. date('r')); } }
- PLOVER