Executive Summary
Summary | |
---|---|
Title | zeromq3 security update |
Informations | |||
---|---|---|---|
Name | DSA-4368 | First vendor Publication | 2019-01-14 |
Vendor | Debian | Last vendor Modification | 2019-01-14 |
Severity (Vendor) | N/A | Revision | 1 |
Security-Database Scoring CVSS v3
Cvss vector : N/A | |||
---|---|---|---|
Overall CVSS Score | NA | ||
Base Score | NA | Environmental Score | NA |
impact SubScore | NA | Temporal Score | NA |
Exploitabality Sub Score | NA | ||
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:L/Au:S/C:C/I:C/A:C) | |||
---|---|---|---|
Cvss Base Score | 9 | Attack Range | Network |
Cvss Impact Score | 10 | Attack Complexity | Low |
Cvss Expoit Score | 8 | Authentication | Requires single instance |
Calculate full CVSS 2.0 Vectors scores |
Detail
Guido Vranken discovered that an incorrect bounds check in ZeroMQ, a lightweight messaging kernel, could result in the execution of arbitrary code. For the stable distribution (stretch), this problem has been fixed in version 4.2.1-4+deb9u1. We recommend that you upgrade your zeromq3 packages. For the detailed security status of zeromq3 please refer to its security tracker page at: https://security-tracker.debian.org/tracker/zeromq3 |
Original Source
Url : http://www.debian.org/security/2019/dsa-4368 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-190 | Integer Overflow or Wraparound (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 1 | |
Os | 1 |
Snort® IPS/IDS
Date | Description |
---|---|
2020-01-21 | ZeroMQ libzmq pointer overflow attempt RuleID : 52501 - Revision : 1 - Type : SERVER-OTHER |
2019-09-17 | ZeroMQ libzmq pointer overflow attempt RuleID : 51042 - Revision : 3 - Type : SERVER-OTHER |
Nessus® Vulnerability Scanner
Date | Description |
---|---|
2019-01-15 | Name : The remote Debian host is missing a security-related update. File : debian_DSA-4368.nasl - Type : ACT_GATHER_INFO |
Alert History
Date | Informations |
---|---|
2019-01-24 21:21:41 |
|
2019-01-15 00:18:15 |
|