Open-Xchange OX Guard up to 2.4.0-rev7 auth Padding credentials management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Open-Xchange OX Guard up to 2.4.0-rev7. This affects an unknown function. Performing a manipulation of the argument auth results in credentials management (Padding). This vulnerability is cataloged as CVE-2016-4028. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Open-Xchange OX Guard up to 2.4.0-rev7. This affects some unknown functionality. The manipulation of the argument auth with an unknown input leads to a credentials management vulnerability (Padding). CWE is classifying the issue as CWE-255. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in Open-Xchange OX Guard before 2.4.0-rev8. OX Guard uses an authentication token to identify and transfer guest users credentials. The OX Guard API acts as a padding oracle by responding with different error codes depending on whether the provided token matches the encryption padding. In combination with AES-CBC, this allows attackers to guess the correct padding. Attackers may run brute-forcing attacks on the content of the guest authentication token and discover user credentials. For a practical attack vector, the guest users needs to have logged in, the content of the guest user's "OxReaderID" cookie and the value of the "auth" parameter needs to be known to the attacker.
The bug was discovered 06/22/2016. The weakness was shared 12/15/2016 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-4028 since 04/15/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 176 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.4.0-rev8 eliminates this vulnerability.
The entries VDB-94507, VDB-94510, VDB-94511 and VDB-94512 are related to this item. 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.open-xchange.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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
Name: PaddingClass: Credentials management / Padding
CWE: CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: OX Guard 2.4.0-rev8
Timeline
04/15/2016 🔍06/22/2016 🔍
12/15/2016 🔍
12/15/2016 🔍
12/15/2016 🔍
10/08/2022 🔍
Sources
Vendor: open-xchange.comAdvisory: securityfocus.com⛔
Status: Not defined
CVE: CVE-2016-4028 (🔍)
GCVE (CVE): GCVE-0-2016-4028
GCVE (VulDB): GCVE-100-94509
SecurityTracker: 1036154
See also: 🔍
Entry
Created: 12/15/2016 16:51Updated: 10/08/2022 18:40
Changes: 12/15/2016 16:51 (59), 07/08/2019 06:35 (2), 10/08/2022 18:40 (4)
Complete: 🔍
Cache ID: 216::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.