Skip to content
Fencer Intel
critical 10.0

GHSA-w4c7-34wj-hqm8 json

Unauthenticated file read leaks master key on Enterprise proxy

published 18d ago modified 18d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository BerriAI/litellm. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

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

Summary

Security advisory published by the maintainers of BerriAI/litellm for litellm: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • pypi litellm 1.103.10, 1.104.8, 1.105.6, 1.106.5

Is GHSA-w4c7-34wj-hqm8 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
the maintainers 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi litellm
<1.103.10
<1.104.8
<1.105.6
<1.106.5
1.103.10
1.104.8
1.105.6
1.106.5

Classification

Weakness
  • CWE-73 External Control of File Name or Path
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-306 Missing Authentication for Critical Functionality
  • CWE-918 Server-Side 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.

The maintainers of BerriAI/litellm published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.