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

GHSA-3hwm-922r-47hw — stud42

HIGHFix: 42Atomys/stud42@a70bfc7

GHSA-3hwm-922r-47hw is a high-severity (CVSS 7.5) vulnerability in atomys.codes/stud42. A fix is available for atomys.codes/stud42 — see the affected versions and patch details below.

Stud42 vulnerable to denial of service

Published
Mar 31, 2023
Updated
Apr 25, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Apr 25, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹atomys.codes/stud42

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

A security vulnerability has been identified in the GraphQL parser used by the API of s42.app. An attacker can overload the parser and cause the API pod to crash. With a bit of threading, the attacker can bring down the entire API, resulting in an unhealthy stream. This vulnerability can be exploited by sending a specially crafted request to the API with a large payload.

An attacker can exploit this vulnerability to cause a denial of service (DoS) attack on the s42.app API, resulting in unavailability of the API for legitimate users.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Goatomys.codes/stud42all versions0.23.0go get atomys.codes/stud42@v0.23.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update atomys.codes/stud42 to 0.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3hwm-922r-47hw 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-3hwm-922r-47hw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3hwm-922r-47hw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A security vulnerability has been identified in the GraphQL parser used by the API of s42.app. An attacker can overload the parser and cause the API pod to crash. With a bit of threading, the attacker can bring down the entire API, resulting in an unhealthy stream. This vulnerability can be exploited by sending a specially crafted request to the API with a large payload. An attacker can exploit this vulnerability to cause a denial of service (DoS) attack on the s42.app API, resulting in unavailability of the API for legitimate users.
O3 Security · Impact-Aware SCA

Is GHSA-3hwm-922r-47hw in your dependencies?

O3 Security finds GHSA-3hwm-922r-47hw across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-3hwm-922r-47hw: stud42 (High 7.5) | O3 Security