Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

google/volley
master @ ef8ac3f
2
Fixes
0
CVEs
MEDIUM
Peak severity
Highlights
Cache Poisoning: 1 prior fix. Scrutinize any change in this area.
core/src/main/java/com/android/volley/toolbox/NetworkUtility.java: most-fixed (1 issue). Treat as high-risk during review.
0 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Cache Poisoning: Reusing the same cache key for different HTTP methods allows non-GET responses (such as from POST or PUT) to be served to GET requests, compromising cache integrity. Developers must ensure that the request method is always part of the cache key partition.
Information Disclosure: Slow network requests could trigger fallback logging that writes sensitive HTTP request metadata to the system logs even when production mode is active. Logging must strictly respect debug configuration flags.