Skip to content

feature: add UNREDACTED_SERVER_ERROR_MESSAGE KB entry#336

Closed
ticket-fixer[bot] wants to merge 1 commit into
masterfrom
fix/os-35490
Closed

feature: add UNREDACTED_SERVER_ERROR_MESSAGE KB entry#336
ticket-fixer[bot] wants to merge 1 commit into
masterfrom
fix/os-35490

Conversation

@ticket-fixer

@ticket-fixer ticket-fixer Bot commented Jul 22, 2026

Copy link
Copy Markdown

Summary

Add a new low-severity knowledge base entry UNREDACTED_SERVER_ERROR_MESSAGE under MOBILE_CLIENT/COMMON/_LOW/ for the disclosure of unredacted server-authored error text rendered verbatim to end users on REST and GraphQL error paths.

The entry is referenced by the generic detection rule delivered in the Ostorlab/rules_kb repository (the analyzer error_message_disclosure), which flags server-sourced (tainted) text flowing into error/toast/snackbar UI sinks. Once this entry is merged and shipped in the ostorlab package, the rules_kb detection rule resolves kb.KB.UNREDACTED_SERVER_ERROR_MESSAGE at runtime.

  • Risk rating: low (information shown to the app's own user; reconnaissance-aiding).
  • Maps to CWE-209 / CWE-215, OWASP MASVS MSTG_CODE_6, MASVS v2.1 MASVS_RESILIENCE_4, PCI REQ_6_2, OWASP Mobile Top 10 M4_2024.
  • Documents the verbatim-message class (not JVM stack traces) and the recommended allow-list / redaction fix.

Ticket: os-35490

Add a new low-severity knowledge base entry for the disclosure of
unredacted server-authored error text rendered verbatim to end users on
REST and GraphQL error paths. The entry is referenced by the generic
detection rule added in rules_kb.

Ticket: os-35490
@ticket-fixer
ticket-fixer Bot requested a review from a team as a code owner July 22, 2026 15:53
burogurama
burogurama previously approved these changes Jul 22, 2026
@burogurama
burogurama dismissed their stale review July 22, 2026 16:54

build failed

@3asm 3asm closed this Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants