1346 matches found
CVE-2017-9111
In OpenEXR 2.2.0, an invalid write of size 8 in the storeSSE function in ImfOptimizedPixelReading.h could cause the application to crash or execute arbitrary code...
UBUNTU-CVE-2017-9110
In OpenEXR 2.2.0, an invalid read of size 2 in the hufDecode function in ImfHuf.cpp could cause the application to crash...
CVE-2017-9111
In OpenEXR 2.2.0, an invalid write of size 8 in the storeSSE function in ImfOptimizedPixelReading.h could cause the application to crash or execute arbitrary code...
CVE-2017-9113
In OpenEXR 2.2.0, an invalid write of size 1 in the bufferedReadPixels function in ImfInputFile.cpp could cause the application to crash or execute arbitrary code...
CVE-2017-9114
In OpenEXR 2.2.0, an invalid read of size 1 in the refill function in ImfFastHuf.cpp could cause the application to crash...
CVE-2017-9113
In OpenEXR 2.2.0, an invalid write of size 1 in the bufferedReadPixels function in ImfInputFile.cpp could cause the application to crash or execute arbitrary code...
CVE-2017-9111
CVE-2017-9111 affects OpenEXR 2.2.0: the storeSSE function in ImfOptimizedPixelReading.h performs an invalid write of size 8, which could crash the application or allow arbitrary code execution. Documented impact is a high-severity issue with potential for remote-triggered impact when processing ...
CVE-2017-9115
In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary code...
CVE-2017-9114
OpenEXR 2.2.0 is affected by CVE-2017-9114 due to an invalid read of size 1 in the refill function (ImfFastHuf.cpp), which can cause a crash. The vulnerability is documented across multiple advisories (Debian/RHEL/NASL/Nessus aggregations) and is addressed in the OpenEXR 2.2.1 patch release (see ...
CVE-2017-9116
OpenEXR 2.2.0 contains a vulnerability CVE-2017-9116 where an invalid read of size 1 in the uncompress function (ImfZip.cpp) could trigger a crash. Several advisories confirm the issue and reference OpenEXR’s 2.2.0 family; patches and updates were released across distributions (e.g., OpenEXR 2.2....
CVE-2017-9116
In OpenEXR 2.2.0, an invalid read of size 1 in the uncompress function in ImfZip.cpp could cause the application to crash...
CVE-2017-9115
CVE-2017-9115 affects OpenEXR 2.2.0: an invalid write of size 2 in the = operator function in half.h can crash the application or allow code execution. Public references indicate a fix in OpenEXR 2.2.1; upgrading to 2.2.1 or newer is the advised remediation. Connected docs also note related, broa...
CVE-2017-9115
In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary code...
CVE-2017-9112
In OpenEXR 2.2.0, an invalid read of size 1 in the getBits function in ImfHuf.cpp could cause the application to crash...
CVE-2017-9115
In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary code...
CVE-2017-9110
In OpenEXR 2.2.0, an invalid read of size 2 in the hufDecode function in ImfHuf.cpp could cause the application to crash...
CVE-2017-9114
In OpenEXR 2.2.0, an invalid read of size 1 in the refill function in ImfFastHuf.cpp could cause the application to crash...
Wireshark 'DOF dissector' DoS Vulnerability - Windows
Wireshark is prone to a denial of service vulnerability. SPDX-FileCopyrightText: 2017 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only CPE = "cpe:/a:wireshark:wireshark";...
NSA Eternalblue SMB vulnerability analysis-vulnerability warning-the black bar safety net
Environment TROJAN: Eternalblue-2.2.0.exe TARGET: win7 sp1 32bits srv.sys 6.1.7601.17514 srvnet.sys 6.1.7601.17514 PATCH: MS17-010 The vulnerability principle srv. sys in the processing SrvOs2FeaListSizeToNt when logic is incorrect resulting in cross-border copy. We first look at the vulnerabilit...
Design/Logic Flaw
In Wireshark 2.2.0 to 2.2.5, the DOF dissector could go into an infinite loop, triggered by packet injection or a malformed capture file. This was addressed in epan/dissectors/packet-dof.c by using a different integer data type and adjusting a return value...