dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-28397

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in the component js2py.disable_pyimport() of js2py up to v0.74 allows attackers to execute arbitrary code via a crafted API call.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in js2py's disable_pyimport() function, designed to block Python imports for security, can be bypassed through crafted API calls allowing arbitrary code execution. This affects all versions up to v0.74.

MitigationUpgrade js2py to a version beyond v0.74 that properly addresses the disable_pyimport() bypass, or implement additional sandboxing and input validation around js2py execution contexts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check js2py installed version
    Run 'pip show js2py' or import js2py; print(js2py.__version__)
    Affected if Version is 0.74 or lower (including all pre-v0.74 releases)
  2. Identify js2py usage in codebase
    Search codebase for 'import js2py' and usages of js2py.eval_js, js2py.eval, or js2py.execute methods
    Affected if js2py is imported and its evaluation/execution methods are used with untrusted input
  3. Check for disable_pyimport usage
    Search for calls to disable_pyimport() in your code or configuration
    Affected if disable_pyimport() is being called (indicating security-sensitive Python import blocking is attempted)
  4. Assess input flow to js2py APIs
    Trace data flow to js2py.eval_js/eval/execute calls to see if attacker-controlled JavaScript can reach these functions
    Affected if User-supplied or external JavaScript code can be passed directly to js2py execution methods without additional sandboxing

You are affected if js2py version is 0.74 or lower AND your application passes untrusted JavaScript to js2py APIs while relying on disable_pyimport() for security isolation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade js2py to a version beyond v0.74 that properly addresses the disable_pyimport() bypass, or implement additional sandboxing and input validation around js2py execution contexts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28397 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28397 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data