We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In GitHub Security Advisory GHSA-jcqq-g64v-gcm7, there is a vulnerability in the following Go packages or modules:
Cross references: No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
id: GO-ID-PENDING modules: - module: github.com/spacemeshos/api versions: - fixed: 1.5.2-hotfix1 packages: - package: github.com/spacemeshos/go-spacemesh - module: github.com/spacemeshos/api versions: - fixed: 1.37.1 vulnerable_at: 1.37.0 packages: - package: github.com/spacemeshos/api summary: |- Previous ATX is not checked to be the newest valid ATX by Smesher when validating incoming ATX in github.com/spacemeshos/api cves: - CVE-2024-34360 ghsas: - GHSA-jcqq-g64v-gcm7 references: - advisory: https://github.com/spacemeshos/go-spacemesh/security/advisories/GHSA-jcqq-g64v-gcm7 - fix: https://github.com/spacemeshos/api/commit/1d5bd972bbe225d024c3e0ae5214ddb6b481716e - fix: https://github.com/spacemeshos/go-spacemesh/commit/9aff88d54be809ac43d60e8a8b4d65359c356b87 - web: https://spacemesh.io/blog/spacemesh-white-paper-1 source: id: GHSA-jcqq-g64v-gcm7
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/585075 mentions this issue: data/reports: add GO-2024-2831.yaml
data/reports: add GO-2024-2831.yaml
Sorry, something went wrong.
f1651ad
timothy-king
No branches or pull requests
In GitHub Security Advisory GHSA-jcqq-g64v-gcm7, there is a vulnerability in the following Go packages or modules:
Cross references:
No existing reports found with this module or alias.
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: