# Cwe 200 Information Exposure

> Use this skill when you need to remediate CWE-200 (Information Exposure) vulnerabilities in Java code. Triggers on SAST findings, security reviews, or when fixing information exposure issues.

- Skill: `developerscoffee/cwe-200-information-exposure` (Agent Skill)
- Install (CLI): `npx skillmds@latest add developerscoffee/cwe-200-information-exposure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/developerscoffee/cwe-200-information-exposure/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: DevelopersCoffee (https://skillmd.com/u/developerscoffee)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/developerscoffee/cwe-200-information-exposure

---


# CWE-200 Information Exposure

## Description

Information Exposure

Reference:
https://cwe.mitre.org/data/definitions/200.html


**OWASP Category**: A01:2021 – Broken Access Control


---

## Vulnerable Pattern


### ❌ Example 1: Vulnerable Pattern

```java
// VULNERABLE: Stack trace exposed
@ExceptionHandler(Exception.class)
public ResponseEntity<?> handleException(Exception e) {
    e.printStackTrace();
    return ResponseEntity.status(500).body(e.getMessage());
}
```


**Why it's vulnerable:** This pattern is vulnerable to Information Exposure




---

## Deterministic Fix


### ✅ Secure Implementation: Secure Implementation

```java
// SECURE: Log details internally, return generic message
@ExceptionHandler(Exception.class)
public ResponseEntity<?> handleException(Exception e) {
    String errorId = UUID.randomUUID().toString();
    log.error("Error ID {}: {}", errorId, e.getMessage(), e);
    return ResponseEntity.status(500)
        .body(Map.of("error", "Internal error", "errorId", errorId));
}
```


**Why it's secure:** Implements proper protection against Information Exposure




---

## Detection Pattern

Look for these patterns in your codebase:


```bash
# Find exception exposure
grep -rn "printStackTrace\\|getMessage.*body\\|e.toString" --include="*.java"
```



---

## Remediation Steps


1. Return generic error messages to users

2. Log detailed errors internally with correlation IDs

3. Disable debug mode in production

4. Review error responses for information leakage


---

## Key Imports

```java

import java.util.UUID;

```

---

## Verification

After remediation:


- Run SAST scanner to confirm vulnerability is resolved

- Review all instances of the vulnerable pattern

- Add unit tests that verify the secure implementation

- Check for similar patterns in related code


---

## Trigger Examples

```
Fix CWE-200 vulnerability
Resolve Information Exposure issue
Secure this Java code against information exposure
SAST reports CWE-200
```

---

## Common Vulnerable Locations

| Layer | Files | Patterns |
|-------|-------|----------|

| Controller | `*Controller.java` | User input handling |

| Service | `*Service.java` | Business logic |

| Repository | `*Repository.java` | Data access |


---

## References


- [CWE-200: Information Exposure](https://cwe.mitre.org/data/definitions/200.html)


---

**Source**: Generated by [Java CWE Security Skills Generator](https://github.com/DevelopersCoffee/java-cwe-security-skills)
**Last Updated**: 2026-03-07