Apache OpenMeetings up to 3.1.0 Password Reset sendHashByUser information disclosure

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.13 |
Summary
A vulnerability identified as problematic has been detected in Apache OpenMeetings up to 3.1.0. The affected element is the function sendHashByUser of the component Password Reset. Performing a manipulation results in information disclosure.
This vulnerability is reported as CVE-2016-0783. The attack is possible to be carried out remotely. Moreover, an exploit is present.
You should upgrade the affected component.
Details
A vulnerability was found in Apache OpenMeetings up to 3.1.0. It has been classified as critical. This affects the function sendHashByUser of the component Password Reset. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
The sendHashByUser function in Apache OpenMeetings before 3.1.1 generates predictable password reset tokens, which makes it easier for remote attackers to reset arbitrary user passwords by leveraging knowledge of a user name and the current system time.
The weakness was disclosed 04/11/2016 as not defined advisory (Website). The advisory is shared at haxx.ml. This vulnerability is uniquely identified as CVE-2016-0783 since 12/16/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a private exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:
As you may notice, the password reset token that is emailed to the user who has forgotten their password is made up of highly predictable components. On line 241, the username and the current system date and time is concatenated and assigned to the loginData variable, and on line 243, an MD5 hash of that variable is generated and written to the database. The hash is then read from the database and appended to the password reset link on line 245, which is then emailed to the user. As the output format of Java’s Date() class does not even include milliseconds (the format is Tue Aug 16 15:30:00 UTC 1977), an attacker with knowledge of an existing user’s username can calculate the password reset token in less than a second as shown in the PoC below.
It is declared as proof-of-concept.
Upgrading to version 3.1.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 85553†) and Vulnerability Center (SBV-58238†). The entries VDB-82078, VDB-82080, VDB-82081 and VDB-90879 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.5
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Private
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 800837
OpenVAS Name: Apache OpenMeetings < 3.1.1 Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Upgrade: OpenMeetings 3.1.1
Fortigate IPS: 🔍
Timeline
12/16/2015 🔍03/25/2016 🔍
04/11/2016 🔍
04/11/2016 🔍
04/11/2016 🔍
04/12/2016 🔍
04/17/2016 🔍
07/13/2022 🔍
Sources
Vendor: apache.orgAdvisory: 136432
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-0783 (🔍)
GCVE (CVE): GCVE-0-2016-0783
GCVE (VulDB): GCVE-100-82077
SecurityFocus: 85553 - Apache OpenMeetings CVE-2016-0783 Information Disclosure Vulnerability
Vulnerability Center: 58238 - Apache OpenMeetings before 3.1.1 Remote Restrictions Bypass via a Bug in sendHashByUser Function, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 04/12/2016 11:04Updated: 07/13/2022 14:49
Changes: 04/12/2016 11:04 (68), 02/05/2019 12:26 (11), 07/13/2022 14:49 (4)
Complete: 🔍
Cache ID: 216:730:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.