Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-3wcq-x3mq-6r9p

HIGH

GHSA-3wcq-x3mq-6r9p is a high-severity (CVSS 7.7) CWE-909 vulnerability in dns-packet. O3 Security confirms whether GHSA-3wcq-x3mq-6r9p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Potential memory exposure in dns-packet

Also known asCVE-2021-23386
Published
May 24, 2021
Updated
Jan 14, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

dns-packetnpm
17.8Mdownloads / week

Description

This affects the package dns-packet before versions 1.3.2 and 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmdns-packet2.0.0&&< 5.2.25.2.2
📦npmdns-packetall versions1.3.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 dns-packet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update dns-packet to 5.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3wcq-x3mq-6r9p 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 pinpoints whether GHSA-3wcq-x3mq-6r9p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3wcq-x3mq-6r9p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package dns-packet before versions 1.3.2 and 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
O3 Security · Impact-Aware SCA

Is GHSA-3wcq-x3mq-6r9p in your dependencies?

O3 detects GHSA-3wcq-x3mq-6r9p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.