CVE-2021-33800
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 · uneditedIn Druid 1.2.3, visiting the path with parameter in a certain function can lead to directory traversal.
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 confidenceDruid 1.2.3 contains a directory traversal vulnerability where a path parameter in a specific function allows attackers to access files outside the intended directory via path traversal sequences (e.g., ../).
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= 1.2.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Alibaba Druid installationLocate Druid JAR files or check application dependencies (pom.xml, build.gradle, lib directory) for Druid presenceAffected if Druid is present in the environment
-
Verify Druid versionCheck the Druid version by inspecting the JAR file name, pom.xml dependency version, or querying the application's /druid endpoint if availableAffected if Version is exactly 1.2.3
-
Identify exposed path-handling endpointsReview application web.xml, routing configuration, or API documentation for endpoints that accept file path parameters (commonly /file, /download, /export paths)Affected if Endpoints accepting path parameters are exposed and accessible
-
Test for directory traversal vulnerabilityIf an endpoint accepts a path parameter, send a test request with traversal sequences such as ../../etc/passwd or ../../../ to observe if unauthorized file access is possibleAffected if The path parameter allows ../ sequences to access files outside the intended directory
The environment is affected if Alibaba Druid version 1.2.3 is installed AND an endpoint with a path parameter is accessible, allowing directory traversal sequences to escape the intended directory.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to a patched version of Druid. If immediate patching is not possible, implement strict input validation and path sanitization on the affected parameter, and restrict file system access permissions for the application.
Druid 1.2.4 or later
- 1. Identify all production and development systems running Druid version 1.2.3
- 2. Upgrade Druid from version 1.2.3 to version 1.2.4 or later, which contains the security fix for this path traversal vulnerability
- 3. After upgrading, verify the console/druid-console functionality works as expected
- 4. Test that the path traversal vulnerability is no longer exploitable
- 5. Monitor for any unusual access patterns to the Druid console endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-33800 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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