Skip to content
Fencer Intel
medium —

GHSA-47xh-qxqv-mgvg json

kube-httpcache is vulnerable to Cross-Site Request Forgery (CSRF)

published 3y ago modified 3y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact

> A request forgery attack can be performed on Varnish Cache servers that have the HTTP/2 protocol turned on. An attacker may introduce characters through the HTTP/2 pseudo-headers that are invalid in the context of an HTTP/1 request line, causing the Varnish server to produce invalid HTTP/1 requests to the backend. This may in turn be used to successfully exploit vulnerabilities in a server behind the Varnish server. > -- https://varnish-cache.org/security/VSV00011.html#vsv00011

### Patches

This is fixed in Varnish 6.0.11; Varnish 6.0.11 is available in `kube-httpcache` versions v0.7.1 and later.

### Workarounds

See [upstream mitigation hints](https://varnish-cache.org/security/VSV00011.html#mitigation).

### References

- https://varnish-cache.org/security/VSV00011.html#vsv00011

Patch / fix

  • go github.com/mittwald/kube-httpcache 0.7.1

Is GHSA-47xh-qxqv-mgvg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/mittwald/kube-httpcache
<0.7.1
0.7.1

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.