dbcve.org
SupersetApplication · Apache

CVE-2022-43719

HIGH · 8.8 CVSS v3.1 Published 2023-01-16
Fix available
A fix is available. Upgrade to after 1.5.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Two legacy REST API endpoints for approval and request access are vulnerable to cross site request forgery. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.

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 · high confidence

Apache Superset versions 1.5.2 and prior and version 2.0.0 contain two legacy REST API endpoints for approval and request access that lack CSRF protection, allowing attackers to induce authenticated users to perform unintended actions via crafted requests.

MitigationImplement anti-CSRF tokens on the affected legacy endpoints or upgrade to a patched version of Apache Superset that addresses this vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SupersetApplication
Affected:<= 1.5.2= 2.0.0

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine installed Apache Superset version
    Run the command to check the Superset version (commonly: superset version, pip show apache-superset, or check the version file in the installation directory)
    Affected if The installed version is 1.5.2 or prior, or exactly 2.0.0
  2. Identify legacy REST API endpoints in use
    Review the Superset configuration and deployed API routes to locate the legacy approval and request access endpoints (typically found under /api/v1/approval or /api/v1/access requests paths in older Superset installations)
    Affected if These legacy REST API endpoints are present and accessible in the deployment
  3. Verify CSRF protection configuration
    Check the Superset configuration file (config.py or equivalent) for CSRF token settings and examine whether the legacy endpoints are included in the CSRF exemption list or properly protected
    Affected if The legacy approval and request access endpoints lack CSRF token protection or are explicitly exempted from CSRF checks
  4. Confirm authenticated user access to legacy endpoints
    Test access to the legacy API endpoints with an authenticated user session to confirm they are reachable and functional
    Affected if Authenticated users can access the legacy endpoints without CSRF token requirements

A user is affected if running Apache Superset version 1.5.2 or prior, or version 2.0.0, with the legacy REST API endpoints for approval and request access exposed and lacking CSRF protection.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.2
Interim mitigation

Implement anti-CSRF tokens on the affected legacy endpoints or upgrade to a patched version of Apache Superset that addresses this vulnerability.

Recommended fix Moderate confidence

Superset 2.0.1 or later (or 1.5.3 if available)

  1. 1. Back up your current Superset database and configuration files.
  2. 2. Review the Apache Superset upgrade documentation for your current version.
  3. 3. Upgrade from Superset <=1.5.2 or 2.0.0 to version 2.0.1 or later.
  4. 4. After upgrading, verify that the legacy REST API endpoints for approval and request access are functioning correctly.
  5. 5. Test that CSRF protections are properly enforced on the affected endpoints.
Caveat Review upgrade notes for potential breaking changes between 1.5.x and 2.0.x, including database migrations and deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Superset Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-43719 — 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-2022-43719 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