OpenmeetingsApplication · Apache
CVE-2017-7684
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 · uneditedApache OpenMeetings 1.0.0 doesn't check contents of files being uploaded. An attacker can cause a denial of service by uploading multiple large files to the server.
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 confidenceApache OpenMeetings 1.0.0 lacks proper validation of uploaded file contents, allowing attackers to bypass file type checks and upload arbitrarily large files. This enables denial of service through resource exhaustion when multiple large files are uploaded repeatedly.
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
OpenmeetingsApplication
= 1.0.0= 2.0= 2.1= 2.1.1= 2.2.0= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6CVSS 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
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 if Apache OpenMeetings is installedCheck for OpenMeetings web application files in the web server's webapp directory, or look for OpenMeetings processes listening on common ports (typically 5080).Affected if Apache OpenMeetings is present and running on the system
-
Determine the installed OpenMeetings versionCheck the application's about page, version file, or examine the war/jar file metadata (MANIFEST.MF) within the OpenMeetings installation directory.Affected if The version matches any of the following: 1.0.0, 2.0, 2.1, 2.1.1, 2.2.0, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5, or 3.0.6
-
Verify if file upload functionality is accessibleCheck if the upload endpoint is accessible by attempting to access the file upload URL (typically /openmeetings/upload or /upload) or reviewing web server access logs for upload-related requests.Affected if The file upload feature is enabled and accessible to users
-
Check for file size limits in configurationExamine the OpenMeetings configuration files (such as om.properties, web.xml, or Tomcat's server.xml) for max-file-size or similar upload limit parameters.Affected if No file size limit is configured, or the limit is set to an extremely large value or disabled (unlimited)
-
Inspect for content-type validation configurationReview the application's configuration or code for MIME type validation logic applied during file uploads.Affected if No server-side content-type or file type validation is configured or enforced
The environment is affected if Apache OpenMeetings versions 1.0.0 through 3.0.6 are running with the file upload feature accessible and without proper file size and content validation limits configured.
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 dataImplement server-side validation including maximum file size limits, content-type verification, and file type validation (magic byte checking). Consider adding rate limiting and upload throttling to prevent mass upload attacks.
Fix this in Openmeetings
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7684 — 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-2017-7684 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