Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-4cmx-hrq9-c23p

MEDIUMFix: moscajs/aedes@ffbc170

GHSA-4cmx-hrq9-c23p is a medium-severity (CVSS 5.3) CWE-285 vulnerability in aedes. O3 Security confirms whether GHSA-4cmx-hrq9-c23p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Authorization in aedes

Also known asCVE-2018-3778
Published
Aug 15, 2018
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

160other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
aedesnpm
120Kdownloads / week

Description

Versions of aedes before 0.35.1 does not respect its own authorization rules when a client sets a Last Will.

Recommendation

Update to version 0.35.1 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmaedesall versions0.35.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aedes. 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 aedes to 0.35.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4cmx-hrq9-c23p 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-4cmx-hrq9-c23p 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-4cmx-hrq9-c23p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `aedes` before 0.35.1 does not respect its own authorization rules when a client sets a `Last Will`. ## Recommendation Update to version 0.35.1 or later.
O3 Security · Impact-Aware SCA

Is GHSA-4cmx-hrq9-c23p in your dependencies?

O3 detects GHSA-4cmx-hrq9-c23p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-4cmx-hrq9-c23p: Improper… | O3 Security