MASWE-0073: Insecure WebResourceResponse Implementations

Content in BETA

This content is in beta and still under active development, so it is subject to change any time (e.g. structure, IDs, content, URLs, etc.).

Send Feedback

Placeholder Weakness

This weakness hasn't been created yet and it's a placeholder. But you can check its status or start working on it yourself. If the issue has not yet been assigned, you can request to be assigned to it and submit a PR with the new content for that weakness by following our guidelines.

Check our GitHub Issues for MASWE-0073

Initial Description or Hints

Using WebResourceResponse instead of WebViewAssetLoader

Relevant Topics

• Since WebResourceResponse may serve attacker‑controlled HTML/JS, it enables XSS when content isn’t properly sanitized (CWE-79).
• If an app exposes arbitrary files via XHR in the WebView context, it may be leaking private data (CWE-200).
• Data or files from a protected internal sphere (such as app-private storage) are exposed to a less trusted sphere, like WebView's JavaScript context or external websites (CWE-669).

References

• https://blog.oversecured.com/Android-Exploring-vulnerabilities-in-WebResourceResponse/

MASTG v1 Coverage

No MASTG v1 tests are related to this weakness.