# Production UART exposes an unauthenticated privileged console

The in-scope physical access model yields a protected console capability without required authentication.

**Candidate CWE:** [CWE-306](https://cwe.mitre.org/data/definitions/306.html)

## Test hypothesis

Capture UART passively first; on an owned suitable lab unit, compare logged-out and authenticated behavior using a harmless identity or synthetic-file read. Record actual privilege and physical effort.

## Evidence required

Retail configuration, access requirements, wiring/voltage notes, console transcript and a protected capability beyond banner output.

## Rule out false positives

Diagnostics, a login prompt, deliberately open developer hardware and intended administrator shells are different cases.

## Playbook and command references

- [Hardware interfaces: production debug access and protected data](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/hardware-interfaces.html) — Distinguish diagnostic output from privileged UART, JTAG/SWD and firmware-secret boundary failures on an owned lab unit.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Hardware%20interfaces%3A%20production%20debug%20access%20and%20protected%20data)

## Referenced by these target playbooks

[Hardware & firmware](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/hardware.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [OWASP internal interfaces](https://github.com/OWASP/owasp-istg/blob/main/src/03_test_cases/internal_interfaces/README.md)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)