Skip to content
Fencer Intel
medium 5.3

GHSA-v999-q5cj-95jg json

COPY stream declared size causes zero-progress extraction loop

published last mo. modified last mo.

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository miurahr/py7zr. 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
5.3
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 miurahr/py7zr for py7zr: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • pypi py7zr > 1.1.3

Is GHSA-v999-q5cj-95jg 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 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
pypi py7zr
<=1.1.3
> 1.1.3

Classification

Weakness
  • CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
  • CWE-835 Loop with Unreachable Exit Condition

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 miurahr/py7zr published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.