Skip to content
Fencer Intel
high 7.5

GHSA-7vwr-g6pm-9hc8 json

Cookie leakage between different users in fastapi-proxy-lib

published 2y ago modified last yr.

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

Summary

### Impact

In the implementation of version `0.0.1`, requests from different user clients are processed using a shared `httpx.AsyncClient`.

However, one oversight is that the `httpx.AsyncClient` will persistently store cookies based on the `set-cookie` response header sent by the target server and share these cookies across different user requests.

This results in a cookie leakage issue among all user clients sharing the same `httpx.AsyncClient`.

### Patches

It's fixed in `0.1.0`

### Workarounds

If you insist `0.0.1`: - Do not use `ForwardHttpProxy` at all. - Do not use `ReverseHttpProxy` or `ReverseWebSocketProxy` for any servers that may potentially send a `set-cookie` response.

**However, it's best to upgrade to the latest version.**

### References

fixed in [#10](https://github.com/WSH032/fastapi-proxy-lib/pull/10)

Patch / fix

  • pypi fastapi-proxy-lib 0.1.0

Is GHSA-7vwr-g6pm-9hc8 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

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi fastapi-proxy-lib
<0.1.0
0.1.0

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.