User Interface (UI) Misrepresentation of Critical Information is a flaw where the screen shows security-relevant details inaccurately, incompletely or misleadingly. Users may approve the wrong action, trust the wrong identity, or miss a risky setting. Defenders should ensure critical fields are clearly rendered, consistent and resistant to overlay or truncation attacks.
What the flaw changes in practice
UI misrepresentation of critical information breaks the assumption that users can rely on the screen as a faithful summary of what they are approving. The flaw matters because security decisions are often made from abbreviated visual cues, so a small rendering error can change a user’s action even when the underlying workflow is sound.
This is not only a cosmetic defect. If a label, value, warning, or recipient display is incomplete or misleading, the interface itself becomes part of the trust boundary. In practice, that can turn a correct backend control into a failed human decision.
Common ways the misrepresentation appears
Misrepresentation usually shows up through truncation, overlap, hidden fields, layout shifts, or content that is rendered differently from the data being submitted. A user may see a familiar name, a shortened destination, or a partial permission summary and assume the rest is harmless or unchanged.
The same weakness can appear in approval dialogs, transaction review screens, admin consoles, mobile views, and security prompts. The underlying pattern is the same: what the user sees is not a reliable representation of what the system will do.
Why it is dangerous for security decisions
Security-critical interfaces often depend on a human noticing exactly the right detail at exactly the right time. When the display is inaccurate, the user may approve a transfer to the wrong recipient, accept a risky permission change, miss a privileged setting, or trust an identity indicator that has been visually obscured.
Because the failure is visible only at the presentation layer, downstream controls may not help. A correct authorization decision, audit trail, or backend validation can still be undermined if the user was misled before confirmation.
Designing interfaces that resist misrepresentation
Critical fields should be rendered with the assumption that attackers or bugs will try to influence how they appear. That means preserving important values in full where possible, handling long text safely, keeping security-relevant labels and values stable, and avoiding layouts that let unrelated content cover or disguise them.
For security-sensitive flows, the safest pattern is to make the decisive information explicit and hard to miss. The interface should clearly separate the value being acted on from surrounding decoration, and it should not rely on visual inference when a precise confirmation is required.
Risk and Threat Considerations
This flaw is attractive to attackers because it can convert a technical compromise into a user-approved action. A misleading screen can hide the real destination, authority, or setting long enough for the victim to confirm an unsafe change without realising it.
Failure mechanism: The attacker or defect changes how critical data is rendered, so the user’s mental model no longer matches the actual operation being confirmed.
Impact: Wrong approvals, unauthorized changes, and identity or privilege confusion can follow, especially in workflows where a single confirmation has high consequence.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP ASVS and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V15 — Secure Coding and Architecture | UI trust boundaries and safe rendering belong to secure application architecture |
| V16 — Security Logging and Error Handling | Misleading security prompts and error states can alter user decisions and obscure risk | |
| Recommendation — Design approval and review screens so critical values cannot be hidden, overlapped, or misleadingly rendered. Ensure security-relevant messages and prompts present exact, consistent information without ambiguous wording or layout. | ||
| NIST SP 800-53 Rev 5 | SI-10 — Information Input Validation | Input validation helps prevent malformed content from driving misleading rendered output |
| Recommendation — Validate and constrain user-supplied values before they reach security-critical displays. | ||
| ISO/IEC 27001:2022 | A.8.12 — Data leakage prevention | Security-sensitive information must be rendered and disclosed carefully to avoid misleading or excessive exposure |
| Recommendation — Apply disclosure controls so sensitive values are shown only in the precise form needed for the decision. | ||
Practitioner Guidance
What to watch for: Treat any security flow that depends on compact summaries, clipped text, or layered UI elements as high risk. Reviewers should test not just the happy path but also long values, narrow screens, localization, zoom, and resizing, because those conditions often expose the misrepresentation.
Governance implication: Teams should own the fidelity of security-relevant UI as a control, not as a design preference. The review standard should ask whether the user can see the exact action, target, and consequence clearly enough to make a trustworthy decision.