CVE-2024-33668
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 was discovered in Zammad before 6.3.0. The Zammad Upload Cache uses insecure, partially guessable FormIDs to identify content. An attacker could try to brute force them to upload malicious content to article drafts they have no access to.
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 confidenceThe Zammad Upload Cache feature uses insecure, partially guessable FormIDs to identify content. Attackers can brute force these predictable FormIDs to upload malicious content to article drafts they have no authorized access to, resulting in unauthorized file injection into the system.
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>= 6.2.0, < 6.3.0= 6.3.0CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check installed Zammad versionRun `zammad run rails r "puts Rails.configuration.x.version"` or check the web interface under Admin > System > Information to find the exact version numberAffected if Version is greater than or equal to 6.2.0 and less than 6.3.0, or exactly 6.3.0
-
Verify Upload Cache feature is accessibleConfirm the `/api/v1/upload_caches` endpoint is reachable. This is typically used when creating or editing tickets with file attachments in drafts. Check if users can access the ticket creation/editing interface with attachment supportAffected if The upload cache endpoint is accessible without additional authentication beyond standard Zammad login
-
Identify if FormIDs follow predictable patternInspect HTTP requests when uploading attachments to article drafts. Submit a draft, note the FormID returned in the response, then submit another draft and compare the FormID values. Look for sequential or time-based patterns rather than cryptographically random stringsAffected if FormIDs appear sequential, time-based, or have identifiable patterns rather than being random alphanumeric strings
-
Check for unauthorized upload cache entriesQuery the upload_caches table in the database for any FormIDs that do not correspond to legitimate user drafts: `SELECT id, form_id, created_at FROM upload_caches;` Compare FormIDs against expected patterns and check for suspicious timing or volumeAffected if There are FormIDs that cannot be linked to authorized user actions or show evidence of automated/unsolicited creation
The environment is affected if Zammad version is between 6.2.0 and 6.3.0 (exclusive) or exactly 6.3.0, and the upload cache feature is accessible to users who could potentially brute force FormIDs.
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 · scoped6.3.0
Upgrade Zammad to version 6.3.0 or later which implements cryptographically secure FormID generation. If immediate upgrade is not possible, restrict access to the upload cache endpoints at the network level.
6.3.1 or later
- Upgrade Zammad to version 6.3.1 or later
- After upgrading, verify the Zammad application is running correctly and test that file upload functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- 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-33668 — 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-33668 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