Jabber Open Source Server up to 2.3.2 UTF-8 c2s/c2s.c Memory information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Jabber Open Source Server up to 2.3.2 and classified as problematic. This issue affects some unknown processing of the file c2s/c2s.c of the component UTF-8 Handler. This manipulation causes information disclosure (Memory). The identification of this vulnerability is CVE-2015-2058. There is no exploit available.
Details
A vulnerability classified as problematic was found in Jabber Open Source Server up to 2.3.2. Affected by this vulnerability is an unknown part of the file c2s/c2s.c of the component UTF-8 Handler. The manipulation with an unknown input leads to a information disclosure vulnerability (Memory). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
c2s/c2s.c in Jabber Open Source Server 2.3.2 and earlier truncates data without ensuring it remains valid UTF-8, which allows remote authenticated users to read system memory or possibly have other unspecified impact via a crafted JID.
The weakness was shared 08/12/2015 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2015-2058 since 02/23/2015. The attack can be launched remotely. A single authentication is necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 72731†). The entry VDB-77060 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: MemoryClass: Information disclosure / Memory
CWE: CWE-200 / CWE-284 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/09/2015 🔍02/23/2015 🔍
08/12/2015 🔍
08/12/2015 🔍
08/13/2015 🔍
06/09/2022 🔍
Sources
Advisory: 85Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-2058 (🔍)
GCVE (CVE): GCVE-0-2015-2058
GCVE (VulDB): GCVE-100-77059
SecurityFocus: 72731 - jabberd CVE-2015-2058 Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 08/13/2015 10:16Updated: 06/09/2022 09:51
Changes: 08/13/2015 10:16 (50), 10/05/2017 18:15 (5), 06/09/2022 09:51 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.