CVE-2024-40441
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 the model_attribs parameter.
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 Doccano Auto Labeling Pipeline module v0.1.23 contain a privilege escalation vulnerability in which the model_attribs parameter can be manipulated by a remote attacker to elevate their privileges within the application.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 Doccano installation and versionRun 'pip show doccano' or check the application's package/version metadata to determine if Doccano is installed and note its version numberAffected if The installed version is v1.8.4 or lower (unpatched)
-
Identify Doccano Auto Labeling Pipeline module versionRun 'pip show doccano-auto-labeling' or check the installed packages to determine the version of the auto-labeling pipeline moduleAffected if The installed version is v0.1.23 or lower (unpatched)
-
Verify model_attribs parameter exposureReview application endpoint configurations, API routes, and any custom routing that accepts the model_attribs parameter; check logs or request patterns for model_attribs usageAffected if The model_attribs parameter is accepted and processed by any API endpoint without strict validation
-
Check for privilege escalation indicatorsReview application audit logs, user permission changes, or role modifications that occurred without proper authorization; query the database for users with elevated roles assigned by unexpected sourcesAffected if Users have gained elevated privileges (admin, superuser, or elevated roles) through the model_attribs parameter mechanism
A user is affected if running Doccano v1.8.4 or Auto Labeling Pipeline v0.1.23 or lower AND the application accepts and processes the model_attribs parameter without strict validation, allowing privilege escalation.
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 dataRestrict and validate the model_attribs parameter on all endpoints, implement proper authorization checks, and upgrade to patched versions when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-40441 — 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-40441 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