| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in ZeroMQ 4.0.0/4.0.1/4.0.2/4.0.3/4.0.4. This affects an unknown part. This manipulation causes an unknown weakness. This vulnerability is tracked as CVE-2014-7203. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in ZeroMQ 4.0.0/4.0.1/4.0.2/4.0.3/4.0.4 and classified as problematic. As an impact it is known to affect integrity. The summary by CVE is:
libzmq (aka ZeroMQ/C++) 4.0.x before 4.0.5 does not ensure that nonces are unique, which allows man-in-the-middle attackers to conduct replay attacks via unspecified vectors.
The weakness was disclosed 10/08/2014 (Website). It is possible to read the advisory at github.com. This vulnerability is known as CVE-2014-7203 since 09/26/2014. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 79107 (openSUSE Security Update : zeromq (openSUSE-SU-2014:1381-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 167365 (OpenSuSE Security Update for zeromq (openSUSE-SU-2014:1381-1)).
Upgrading to version 4.0.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (96242), Tenable (79107), SecurityFocus (BID 70157†), Secunia (SA62262†) and Vulnerability Center (SBV-47203†). The entry VDB-71886 is pretty similar. Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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
Class: UnknownCWE: Unknown
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 |
Nessus ID: 79107
Nessus Name: openSUSE Security Update : zeromq (openSUSE-SU-2014:1381-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ZeroMQ 4.0.4
Patch: github.com
Timeline
09/26/2014 🔍09/26/2014 🔍
10/08/2014 🔍
10/08/2014 🔍
10/08/2014 🔍
11/14/2014 🔍
11/20/2014 🔍
03/26/2015 🔍
03/30/2022 🔍
Sources
Advisory: 1191Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-7203 (🔍)
GCVE (CVE): GCVE-0-2014-7203
GCVE (VulDB): GCVE-100-71887
X-Force: 96242
SecurityFocus: 70157 - ZeroMQ Multiple Security Bypass Vulnerabilities
Secunia: 62262 - SUSE update for zeromq, Not Critical
Vulnerability Center: 47203 - ZeroMQ Remote Information Disclosure via Man-in-the-Middle Attack in stream_engine.cpp - CVE-2014-7203, Medium
See also: 🔍
Entry
Created: 03/26/2015 16:14Updated: 03/30/2022 07:40
Changes: 03/26/2015 16:14 (60), 06/12/2017 08:37 (7), 03/30/2022 07:35 (4), 03/30/2022 07:40 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.