CWE-542 Variant Deprecated

DEPRECATED: Information Exposure Through Cleanup Log Files

This entry has been deprecated because it was too specific. Please refer to the broader and more comprehensive CWE-532: Information Exposure Through Log Files for current guidance.

Definition

What is CWE-542?

This entry has been deprecated because it was too specific. Please refer to the broader and more comprehensive CWE-532: Information Exposure Through Log Files for current guidance.
This weakness was originally created to describe a specific scenario where sensitive information could be exposed through log files created during cleanup or maintenance processes. However, it was merged into a more general category because the core vulnerability—leaking data through any application log—is the same, regardless of when the log file was created. For developers, the key takeaway is that any log file, including temporary debug logs, installation logs, or cleanup reports, must be treated with the same security considerations as your main application logs. Always sanitize sensitive data (like passwords, keys, or PII) before writing to any file, and restrict access to log directories as part of your standard deployment configuration.
Real-world impact

Real-world CVEs caused by CWE-542

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-542

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-542

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-542 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-542?

This entry has been deprecated because it was too specific. Please refer to the broader and more comprehensive CWE-532: Information Exposure Through Log Files for current guidance.

How serious is CWE-542?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-542?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-542?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-542?

Plexicus's SAST engine matches the data-flow signature for CWE-542 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-542?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/542.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-542

No related weaknesses indexed for this CWE.

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.