Skip to content
Fencer Intel
high —

GHSA-7prj-hgx4-2xc3 json

Potential Vulnerabilities Due to Outdated golang.org/x/crypto Dependency in NanoProxy

published last yr. modified 8mo ago also GO-2024-3330

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

A security issue was identified in the NanoProxy project related to the `golang.org/x/crypto` dependency. The project was using an outdated version of this dependency, which potentially exposed the system to security vulnerabilities that have been addressed in subsequent updates.

Impact: The specific vulnerabilities in the outdated version of `golang.org/x/crypto` could include authorization bypasses, data breaches, or other security risks. These vulnerabilities can be exploited by attackers to compromise the integrity, confidentiality, or availability of the system.

Resolution: The issue has been fixed in NanoProxy by upgrading the `golang.org/x/crypto` dependency to version 0.31.0. Users are strongly encouraged to update their instances of NanoProxy to include this fix and ensure they are using the latest secure version of all dependencies.

Fixed Version: * `golang.org/x/crypto` upgraded to version 0.31.0.

Patch / fix

  • go github.com/ryanbekhen/nanoproxy 0.15.0

Is GHSA-7prj-hgx4-2xc3 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/ryanbekhen/nanoproxy
<0.15.0
0.15.0

Classification

Weakness
  • CWE-1395 Dependency on Vulnerable Third-Party Component
  • CWE-285 Improper Authorization

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.