dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-33335

MEDIUM · 6.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 →
69/100
Remediation priority · Elevated
Remotely reachable 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
SQL Injection vulnerability in H3C technology company SeaSQL DWS V2.0 allows a remote attacker to execute arbitrary code via a crafted file.

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

SQL injection vulnerability in H3C SeaSQL DWS V2.0 allows remote attackers to execute arbitrary code through a crafted file, likely due to improper sanitization of file-parsed input being used in SQL queries.

MitigationImplement parameterized queries/prepared statements for all database operations, apply strict input validation on file uploads, and apply least-privilege principles to database accounts.

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

CVSS:3.1/AV:N/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. Identify H3C SeaSQL DWS installation
    Check system inventory or running services for H3C SeaSQL DWS. Look for process names, installed packages, or documentation referencing this product.
    Affected if H3C SeaSQL DWS is installed and running
  2. Confirm version is V2.0
    Locate the installed version through product documentation, about pages, or version files. Compare against the affected version range.
    Affected if Installed version is SeaSQL DWS V2.0
  3. Determine if file upload/parsing feature is accessible
    Review available web interfaces, API endpoints, or administrative consoles for file upload functionality related to data import or parsing.
    Affected if File upload or data import features are accessible to users
  4. Check for web application firewall or input validation
    Inspect the application's configuration files, proxy settings, or WAF rules for SQL injection protections on file-parsed inputs.
    Affected if No input validation or WAF protection exists for file-parsed data
  5. Review database query logs
    Examine database logs for unexpected or suspicious SQL statements, especially those containing file content, unusual characters, or UNION-based injections.
    Affected if Database logs show malformed SQL queries containing file content or suspicious payloads

A system is affected if it runs H3C SeaSQL DWS V2.0 with accessible file upload/parsing functionality that processes input without sanitization before SQL execution.

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

Implement parameterized queries/prepared statements for all database operations, apply strict input validation on file uploads, and apply least-privilege principles to database accounts.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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