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

GHSA-7hh3-3x64-v2g9

MEDIUMFix: remult/remult@6892ae9

GHSA-7hh3-3x64-v2g9 is a medium-severity (CVSS 5) CWE-284 vulnerability in remult. O3 Security confirms whether GHSA-7hh3-3x64-v2g9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

When setting EntityOptions.apiPrefilter to a function, the filter is not applied to API requests for a resource by Id

Also known asCVE-2023-35167
Published
Jun 20, 2023
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, a proxy for how much of the ecosystem is exposed.

remultnpm
2Kdownloads / week

Description

Impact

If you used the apiPrefilter option of the @Entity decorator, by setting it to a function that returns a filter that prevents unauthorized access to data, an attacker who knows the id of an entity instance she is not authorized to access, can gain read, update and delete access to it.

Patches

The issue is fixed in version 0.20.6

Workarounds

Set the apiPrefilter option to a filter object instead of a function.

References

If you're using a minor version < 0.20 and require a patch, please create an issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmremultall versions0.20.6

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for remult. 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 remult to 0.20.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7hh3-3x64-v2g9 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-7hh3-3x64-v2g9 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-7hh3-3x64-v2g9. 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 used the [apiPrefilter](https://remult.dev/docs/ref_entity.html#apiprefilter) option of the `@Entity` decorator, by setting it to a function that returns a filter that prevents unauthorized access to data, an attacker who knows the `id` of an entity instance she is not authorized to access, can gain read, update and delete access to it. ### Patches The issue is fixed in version 0.20.6 ### Workarounds Set the `apiPrefilter` option to a filter object instead of a function. ### References If you're using a minor version < 0.20 and require a patch, please create an issue.
O3 Security · Impact-Aware SCA

Is GHSA-7hh3-3x64-v2g9 in your dependencies?

O3 detects GHSA-7hh3-3x64-v2g9 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-7hh3-3x64-v2g9: remult (Medium 5) | O3 Security