Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-wxwq-525w-hcqx yapscan

HIGHFix: fkie-cad/yapscan#46

GHSA-wxwq-525w-hcqx is a high-severity (CVSS 7.5) vulnerability in github.com/fkie-cad/yapscan. A fix is available for github.com/fkie-cad/yapscan — see the affected versions and patch details below.

Yapscan Denial of Service vulnerability in report server

Also known asGO-2023-1607
Published
Mar 3, 2023
Updated
Aug 20, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 20, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/fkie-cad/yapscan

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

If you use the report server, it may be vulnerable to a Denial of Service attack.

Patches

Has been patched in v0.19.2.

References

The vulnerability was inherited by the following upstream vulnerabilites

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/fkie-cad/yapscan0.18.0&&< 0.19.20.19.2go get github.com/fkie-cad/yapscan@v0.19.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fkie-cad/yapscan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/fkie-cad/yapscan to 0.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wxwq-525w-hcqx is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wxwq-525w-hcqx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wxwq-525w-hcqx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact If you use the report server, it may be vulnerable to a Denial of Service attack. ### Patches Has been patched in v0.19.2. ### References The vulnerability was inherited by the following upstream vulnerabilites - [golang.org/x/text < v0.3.7](https://github.com/advisories/GHSA-ppp9-7jff-5vj2) - [golang.org/x/net < 0.0.0-20220906165146-f3363e06e74c](https://github.com/advisories/GHSA-69cg-p879-7622)
O3 Security · Impact-Aware SCA

Is GHSA-wxwq-525w-hcqx in your dependencies?

O3 Security finds GHSA-wxwq-525w-hcqx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-wxwq-525w-hcqx: yapscan (High 7.5) | O3 Security