CVE-2024-40442
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 · uneditedAn issue in Doccano Open source annotation tools for machine learning practitioners v.1.8.4 and Doccano Auto Labeling Pipeline module to annotate a document automatically v.0.1.23 allows a remote attacker to escalate privileges via a crafted REST Request.
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 confidenceDoccano v1.8.4 and the Auto Labeling Pipeline module v0.1.23 contain a privilege escalation vulnerability where a remote attacker can send crafted REST API requests to elevate their privileges within the application. The vulnerability stems from insufficient authorization checks on certain REST endpoints.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Doccano versionCheck the Doccano version file, package metadata, or admin interface. Common methods: `pip show doccano`, check the UI footer, or inspect the deployed package version.Affected if Version is 1.8.4 or earlier without the patch applied
-
Identify Auto Labeling Pipeline module versionCheck the installed package version for the auto-labeling pipeline: `pip show doccano-auto-labeling` or inspect the modules settings in the Doccano admin panel.Affected if Module version is 0.1.23 or earlier without the patch applied
-
Confirm REST API is enabledVerify the REST API is exposed by checking Doccano's configuration file, environment variables (e.g., API_ENABLED), or attempting to access standard API endpoints such as /api/v1/ or /api/projects/.Affected if REST API endpoints are accessible without additional authentication layers beyond basic login
-
Review RBAC configuration on API endpointsInspect the Doccano role-based access control settings in the admin panel under Users > Groups or the configuration file. Check if all REST endpoints have explicit role/permission bindings configured.Affected if RBAC is not enforced or is misconfigured on certain REST endpoints, allowing unauthorized privilege escalation
-
Check for unexpected privilege changesReview audit logs, user permission change logs, or Doccano's activity log for any recent unauthorized role upgrades or permission modifications initiated via API calls.Affected if Evidence exists of privilege escalation events or unauthorized role modifications
A user is affected if running Doccano v1.8.4 or earlier with the Auto Labeling Pipeline module v0.1.23 or earlier, with REST API accessible and RBAC not properly enforced on all endpoints.
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.
From vendor dataUpgrade to patched versions of Doccano and ensure proper role-based access control (RBAC) is enforced on all REST API endpoints. If no patch available, restrict API access to trusted users and implement additional authentication layers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40442 — 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-2024-40442 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