CVE-2016-2164 json
Apache OpenMeetings allows remote attackers to read arbitrary files by attempting to upload a file
published 2016-04-11 10 y ago modified 2026-06-17 4 mo ago also GHSA-f6vf-465r-h42p , EUVD-2022-3709
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.0%
- EPSS 7.0% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
The (1) FileService.importFileByInternalUserId and (2) FileService.importFile SOAP API methods in Apache OpenMeetings before 3.1.1 improperly use the Java URL class without checking the specified protocol handler, which allows remote attackers to read arbitrary files by attempting to upload a file.
Patch / fix
- maven org.apache.openmeetings:openmeetings-parent 3.1.1
Exploit prediction
7.01% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.openmeetings:openmeetings-parent | <3.1.1 |
3.1.1 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
openmeetings.apache.org
/security.html
web, patch, vendor-advisory
-
packetstormsecurity.com
/files/136434/Apache-OpenMeetings-3.0.7-Arbitary-File-Read.html
web
-
apache.org
/dist/openmeetings/3.1.1/CHANGELOG
web
-
securityfocus.com
/archive/1/537887/100/0/threaded
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2016-2164
advisory
-
github.com
/apache/openmeetings
package
Sources
- CVE List CVE-2016-2164
- GitHub Advisory GHSA-f6vf-465r-h42p
- NVD CVE-2016-2164
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.