pingora-proxy is vulnerable to Improper Input Validation
70
CVE Score
High
Improper Input Validation
Pingora versions prior to 0.9.0 passed the downstream request through upstream_request_filter and wrote it to HTTP/1 upstreams without removing the client's Connection header, other hop-by-hop headers, or the headers Connection nominated, although RFC 9110 Section 7.6.1 requires intermediaries to remove them. The HTTP/2 upstream path already removed Connection and related HTTP/1-specific headers. A client could therefore nominate a header that the application adds in upstream_request_filter (for example, Connection: keep-alive, X-Forwarded-For). A downstream HTTP/1 intermediary that honors Connection would then strip the Pingora-added header before it reached the origin.
Upgrade the pingora-proxy library to the patch version.
You are affected if you are using a version that falls within the vulnerable range.
0.1.0 - 0.8.1
Fixed in 0.9.0pingora-proxy is vulnerable to Improper Input Validation in versions 0.1.0 - 0.8.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.