Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-qr95-4mq5-r3fh
No affected components available
Impact
What kind of vulnerability is it? Who is impacted?
Anyone using >= v1.0.0 < v1.6.0.
Patches
Has the problem been patched? What versions should users upgrade to?
Yes. Upgrading to at least >= v1.6.0 (the earliest safe version) will resolve the problem. However, as multiple new major versions have been released since that version, upgrading to the latest available version is recommended, in order to protect against any potential future vulnerabilities, unknown at the time of writing this advisory.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Yes. In the package's configuration, disable archive checking by setting check_archives to false (thus avoiding execution of the affected parts of the codebase entirely).
References
Are there any links users can visit to find out more?
Yes. The vulnerability is documented at SECURITY.md and also at #167.
For more information
If you have any questions or comments about this advisory:
- Comment at the issue linked to this advisory, or..
- Contact the package author.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the integrity of the data.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard