dbcve.org
OpenmeetingsApplication · Apache

CVE-2017-7664

CRITICAL · 10.0 CVSS v3.0 Published 2017-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Uploaded XML documents were not correctly validated in Apache OpenMeetings 3.1.0.

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 · low confidence

In Apache OpenMeetings 3.1.0, uploaded XML documents were not correctly validated, likely allowing XML External Entity (XXE) injection attacks through the file upload functionality.

MitigationImplement secure XML parser configuration by disabling external entities, DTD processing, and entity expansion in all XML upload handlers; validate and sanitize XML content before processing.

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
Affected:= 3.1.0= 3.1.1= 3.1.2= 3.1.3= 3.1.4= 3.1.5= 3.2.0= 3.2.1

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
Changed
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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 OpenMeetings version
    Locate the OpenMeetings installation directory and check the version file or about page in the web interface. Common locations include the installer directory, version.properties, or the Administration > Configuration panel.
    Affected if The installed version matches any of: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.2.0, or 3.2.1
  2. Determine if XML file upload is enabled
    Review the OpenMeetings configuration to see if document upload features are available to users, particularly the import functionality that processes uploaded files.
    Affected if Users or administrators can upload files including XML documents to the system
  3. Check XML parser security configuration
    Inspect the XML processing configuration files in the OpenMeetings deployment for settings related to external entity handling, DTD processing, and entity expansion. Look for parser settings in configuration files or Java code that handles XML uploads.
    Affected if The XML parser is configured to allow external entities, DTD processing, or entity expansion (XXE vulnerabilities are present)
  4. Review uploaded file handling code
    Examine the source code or configuration for file upload handlers that process XML files, checking if XML validation is performed before parsing.
    Affected if Uploaded XML files are parsed without proper validation or secure parser configuration

You are affected if you are running any version from 3.1.0 through 3.2.1 and your OpenMeetings deployment accepts XML file uploads without secure XML parser settings that disable external entities and DTD processing.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement secure XML parser configuration by disabling external entities, DTD processing, and entity expansion in all XML upload handlers; validate and sanitize XML content before processing.

Recommended fix Moderate confidence

Apache OpenMeetings 3.1.4 or later

  1. 1. Back up your current Apache OpenMeetings installation and database
  2. 2. Download Apache OpenMeetings version 3.1.4 or later from the official Apache repository
  3. 3. Stop the OpenMeetings service
  4. 4. Replace the existing installation files with the new version
  5. 5. Verify XML parser configuration disables external entity processing
  6. 6. Start the OpenMeetings service
  7. 7. Test XML upload functionality to confirm the fix works
Caveat Review release notes for any configuration or feature changes between 3.1.x versions

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

Fix this in Openmeetings Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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