CWE-311
Transmitting or storing sensitive data (PII, financial records, health data) without encryption, violating compliance requirements and enabling interception....
Precogs AI Insight
"Precogs AI identifies sensitive data flows that lack encryption and recommends TLS for transit and AES-256 for storage."
What is CWE-311 (Missing Encryption of Sensitive Data)?
Transmitting or storing sensitive data (PII, financial records, health data) without encryption, violating compliance requirements and enabling interception.
Vulnerability Insights
In the context of pii & secrets detection vulnerabilities, this vulnerability poses significant risk because compiled binaries and complex AI logic cannot be easily patched without vendor cooperation. Organizations relying on third-party software must use structural analysis tools to detect these flaws.
Impact on Systems
- Compromise of Application Integrity: Predictable execution flow is disrupted
- Potential Data Exposure: Depending on context, sensitive configurations may leak
- Availability Risks: Unexpected states leading to temporary denial of service
Real-World Attack Scenario
An attacker probes the system interfaces to identify areas where the input or state related to Missing Encryption of Sensitive Data is improperly handled. Once identified, they craft a payload tailored to the specific backend architecture. By exploiting the lack of robust structural validation, the attacker is able to force the application into an unintended state, bypassing standard business logic and achieving unauthorized outcomes.
Code Examples
Vulnerable Implementation
// VULNERABLE: Unvalidated input leading to Missing Encryption of Sensitive Data
function processInput(data) {
// Missing strict validation or sanitization
executeOrStoreConfig(data);
}
Secure Alternative
// SECURE: Proper validation mitigating Missing Encryption of Sensitive Data
function processInput(data) {
if (!isValid(data)) throw new Error('Invalid input');
const safeData = sanitize(data);
executeOrStoreConfig(safeData);
}
Remediation
Ensure robust input validation, boundary checking, and adherence to secure architecture frameworks when designing PII & Secrets solutions. Use automated code scanning or binary analysis to detect flaws early in the SDLC.