dbcve.org
WicketApplication · Apache

CVE-2016-6793

CRITICAL · 9.1 CVSS v3.0 Published 2017-07-17
Fix available
A fix is available. Upgrade to 1.5.17 / 6.25.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The DiskFileItem class in Apache Wicket 6.x before 6.25.0 and 1.5.x before 1.5.17 allows remote attackers to cause a denial of service (infinite loop) and write to, move, and delete files with the permissions of DiskFileItem, and if running on a Java VM before 1.3.1, execute arbitrary code via a crafted serialized Java object.

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 confidence

Apache Wicket's DiskFileItem class prior to 6.25.0 and 1.5.17 contains a deserialization vulnerability where a crafted serialized Java object can trigger an infinite loop (DoS) and perform unauthorized file operations including write, move, and delete actions with the application's permissions. On very old Java VMs (pre-1.3.1), this can lead to arbitrary code execution.

MitigationUpgrade Apache Wicket to version 6.25.0 or later (for 6.x branches) or 1.5.17 or later (for 1.5.x branches), and ensure Java runtime is modern. Review DiskFileItem usage in the application for any signs of exploitation.

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
WicketApplication
Affected:>= 1.5.0, < 1.5.17>= 6.0.0, < 6.25.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Wicket dependency
    Search for wicket-core JAR files in your application lib directory, or grep for 'wicket' in pom.xml, build.gradle, or package manager files
    Affected if Apache Wicket is present in the application
  2. Determine Apache Wicket version
    Check the version number in the wicket-core JAR filename or in your dependency management file (pom.xml, build.gradle)
    Affected if Version is 1.5.0 through 1.5.16, or 6.0.0 through 6.24.0
  3. Verify DiskFileItem is in use
    Search codebase for imports or references to org.apache.wicket.util.upload.DiskFileItem, or check for multipart form uploads which trigger this class
    Affected if DiskFileItem class handles file uploads in the application
  4. Inspect uploaded file handling
    Review application code that processes file uploads to confirm DiskFileItem deserializes uploaded data
    Affected if The application deserializes file uploads via DiskFileItem without validation

Your environment is affected if Apache Wicket version falls within 1.5.0-1.5.16 or 6.0.0-6.24.0 AND your application uses DiskFileItem to handle file uploads.

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.

dbcve · scoped
Upgrade available Upgrade to 1.5.17 / 6.25.0 or later
Fixed in 1.5.176.25.0
Interim mitigation

Upgrade Apache Wicket to version 6.25.0 or later (for 6.x branches) or 1.5.17 or later (for 1.5.x branches), and ensure Java runtime is modern. Review DiskFileItem usage in the application for any signs of exploitation.

Recommended fix High confidence

Wicket 1.5.17 (for 1.5.x branch) or Wicket 6.25.0 (for 6.x branch)

  1. 1. Identify the current Wicket version in use by checking project dependencies (pom.xml, build.gradle, or equivalent)
  2. 2. Determine which branch is in use: 1.5.x or 6.x
  3. 3. For projects using Wicket 1.5.x: upgrade to version 1.5.17 or later
  4. 4. For projects using Wicket 6.x: upgrade to version 6.25.0 or later
  5. 5. Update the dependency version in build configuration (e.g., pom.xml: change org.apache.wicket:wicket from 6.24.0 to 6.25.0)
  6. 6. Rebuild and test the application to ensure compatibility
  7. 7. Redeploy the updated application
Caveat Review release notes for any breaking changes between current version and target upgrade version; minor version upgrades typically have minimal breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wicket Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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