idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
384,399 | libxml2 | e2a9122b8dde53d320750451e9907a7dcb2ca8bb | https://github.com/GNOME/libxml2 | https://git.gnome.org/browse/libxml2/commit/?id=e2a9122b8dde53d320750451e9907a7dcb2ca8bb | Set memory limit for LZMA decompression
Otherwise malicious LZMA compressed files could consume large amounts
of memory when decompressed.
According to the xz man page, files compressed with `xz -9` currently
require 65 MB to decompress, so set the limit to 100 MB.
Should fix bug 786696. | 0 | xz_head(xz_statep state)
{
lzma_stream *strm = &(state->strm);
lzma_stream init = LZMA_STREAM_INIT;
int flags;
unsigned len;
/* allocate read buffers and inflate memory */
if (state->size == 0) {
/* allocate buffers */
state->in = xmlMalloc(state->want);
state->out = xml... | 127,835,996,770,325,130,000,000,000,000,000,000,000 | xzlib.c | 216,482,564,633,581,100,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2017-18258 | The xz_head function in xzlib.c in libxml2 before 2.9.6 allows remote attackers to cause a denial of service (memory consumption) via a crafted LZMA file, because the decoder functionality does not restrict memory usage to what is required for a legitimate file. | https://nvd.nist.gov/vuln/detail/CVE-2017-18258 |
206,659 | qemu | 813212288970c39b1800f63e83ac6e96588095c6 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=813212288970c39b1800f63e83ac6e96588095c6 | ide: atapi: assert that the buffer pointer is in range
A case was reported where s->io_buffer_index can be out of range.
The report skimped on the details but it seems to be triggered
by s->lba == -1 on the READ/READ CD paths (e.g. by sending an
ATAPI command with LBA = 0xFFFFFFFF). For now paper over it
with asserti... | 1 | void ide_atapi_cmd_reply_end(IDEState *s)
{
int byte_count_limit, size, ret;
while (s->packet_transfer_size > 0) {
trace_ide_atapi_cmd_reply_end(s, s->packet_transfer_size,
s->elementary_transfer_size,
s->io_buffer_index);
... | 69,193,233,814,506,210,000,000,000,000,000,000,000 | atapi.c | 221,227,170,542,491,200,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-29443 | ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated. | https://nvd.nist.gov/vuln/detail/CVE-2020-29443 |
384,409 | qemu | 813212288970c39b1800f63e83ac6e96588095c6 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=813212288970c39b1800f63e83ac6e96588095c6 | ide: atapi: assert that the buffer pointer is in range
A case was reported where s->io_buffer_index can be out of range.
The report skimped on the details but it seems to be triggered
by s->lba == -1 on the READ/READ CD paths (e.g. by sending an
ATAPI command with LBA = 0xFFFFFFFF). For now paper over it
with asserti... | 0 | void ide_atapi_cmd_reply_end(IDEState *s)
{
int byte_count_limit, size, ret;
while (s->packet_transfer_size > 0) {
trace_ide_atapi_cmd_reply_end(s, s->packet_transfer_size,
s->elementary_transfer_size,
s->io_buffer_index);
... | 86,317,681,188,311,170,000,000,000,000,000,000,000 | atapi.c | 253,919,746,882,180,470,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-29443 | ide_atapi_cmd_reply_end in hw/ide/atapi.c in QEMU 5.1.0 allows out-of-bounds read access because a buffer index is not validated. | https://nvd.nist.gov/vuln/detail/CVE-2020-29443 |
206,660 | polarssl | d66f070d492ef75405baad9f0d018b1bd06862c8 | https://github.com/polarssl/polarssl | https://github.com/polarssl/polarssl/commit/d66f070d492ef75405baad9f0d018b1bd06862c8 | Disable debug messages that can introduce a timing side channel.
Introduced the POLARSSL_SSL_DEBUG_ALL flag to enable all these debug
messages in case somebody does want to see the reason checks fail. | 1 | static int ssl_decrypt_buf( ssl_context *ssl )
{
size_t i, padlen = 0, correct = 1;
unsigned char tmp[POLARSSL_SSL_MAX_MAC_SIZE];
SSL_DEBUG_MSG( 2, ( "=> decrypt buf" ) );
if( ssl->in_msglen < ssl->transform_in->minlen )
{
SSL_DEBUG_MSG( 1, ( "in_msglen (%d) < minlen (%d)",
... | 40,762,020,110,086,510,000,000,000,000,000,000,000 | ssl_tls.c | 109,977,389,744,460,380,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-0169 | The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and p... | https://nvd.nist.gov/vuln/detail/CVE-2013-0169 |
384,451 | polarssl | d66f070d492ef75405baad9f0d018b1bd06862c8 | https://github.com/polarssl/polarssl | https://github.com/polarssl/polarssl/commit/d66f070d492ef75405baad9f0d018b1bd06862c8 | Disable debug messages that can introduce a timing side channel.
Introduced the POLARSSL_SSL_DEBUG_ALL flag to enable all these debug
messages in case somebody does want to see the reason checks fail. | 0 | static int ssl_decrypt_buf( ssl_context *ssl )
{
size_t i, padlen = 0, correct = 1;
unsigned char tmp[POLARSSL_SSL_MAX_MAC_SIZE];
SSL_DEBUG_MSG( 2, ( "=> decrypt buf" ) );
if( ssl->in_msglen < ssl->transform_in->minlen )
{
SSL_DEBUG_MSG( 1, ( "in_msglen (%d) < minlen (%d)",
... | 174,591,029,547,541,900,000,000,000,000,000,000,000 | ssl_tls.c | 193,081,241,478,287,840,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2013-0169 | The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and p... | https://nvd.nist.gov/vuln/detail/CVE-2013-0169 |
206,664 | linux | bc890a60247171294acc0bd67d211fa4b88d40ba | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bc890a60247171294acc0bd67d211fa4b88d40ba | ext4: verify the depth of extent tree in ext4_find_extent()
If there is a corupted file system where the claimed depth of the
extent tree is -1, this can cause a massive buffer overrun leading to
sadness.
This addresses CVE-2018-10877.
https://bugzilla.kernel.org/show_bug.cgi?id=199417
Signed-off-by: Theodore Ts'o ... | 1 | ext4_find_extent(struct inode *inode, ext4_lblk_t block,
struct ext4_ext_path **orig_path, int flags)
{
struct ext4_extent_header *eh;
struct buffer_head *bh;
struct ext4_ext_path *path = orig_path ? *orig_path : NULL;
short int depth, i, ppos = 0;
int ret;
eh = ext_inode_hdr(inode);
depth = ext_depth(inode)... | 187,029,277,086,023,140,000,000,000,000,000,000,000 | extents.c | 76,566,557,717,085,870,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-10877 | Linux kernel ext4 filesystem is vulnerable to an out-of-bound access in the ext4_ext_drop_refs() function when operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10877 |
384,534 | linux | bc890a60247171294acc0bd67d211fa4b88d40ba | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bc890a60247171294acc0bd67d211fa4b88d40ba | ext4: verify the depth of extent tree in ext4_find_extent()
If there is a corupted file system where the claimed depth of the
extent tree is -1, this can cause a massive buffer overrun leading to
sadness.
This addresses CVE-2018-10877.
https://bugzilla.kernel.org/show_bug.cgi?id=199417
Signed-off-by: Theodore Ts'o ... | 0 | ext4_find_extent(struct inode *inode, ext4_lblk_t block,
struct ext4_ext_path **orig_path, int flags)
{
struct ext4_extent_header *eh;
struct buffer_head *bh;
struct ext4_ext_path *path = orig_path ? *orig_path : NULL;
short int depth, i, ppos = 0;
int ret;
eh = ext_inode_hdr(inode);
depth = ext_depth(inode)... | 129,241,051,771,197,900,000,000,000,000,000,000,000 | extents.c | 107,006,711,583,493,610,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2018-10877 | Linux kernel ext4 filesystem is vulnerable to an out-of-bound access in the ext4_ext_drop_refs() function when operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10877 |
206,668 | NetworkManager | 420784e342da4883f6debdfe10cde68507b10d27 | https://gitlab.freedesktop.org/NetworkManager/NetworkManager | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/420784e342da4883f6debdfe10cde68507b10d27 | core: fix crash in nm_wildcard_match_check()
It's not entirely clear how to treat %NULL.
Clearly "match.interface-name=eth0" should not
match with an interface %NULL. But what about
"match.interface-name=!eth0"? It's now implemented
that negative matches still succeed against %NULL.
What about "match.interface-name=*"... | 1 | nm_wildcard_match_check(const char *str, const char *const *patterns, guint num_patterns)
{
gboolean has_optional = FALSE;
gboolean has_any_optional = FALSE;
guint i;
for (i = 0; i < num_patterns; i++) {
gboolean is_inverted;
gboolean is_mandatory;
gboolean match... | 2,985,068,423,086,014,400,000,000,000,000,000,000 | nm-core-utils.c | 263,135,910,508,977,660,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2021-20297 | A flaw was found in NetworkManager in versions before 1.30.0. Setting match.path and activating a profile crashes NetworkManager. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20297 |
384,577 | NetworkManager | 420784e342da4883f6debdfe10cde68507b10d27 | https://gitlab.freedesktop.org/NetworkManager/NetworkManager | https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/420784e342da4883f6debdfe10cde68507b10d27 | core: fix crash in nm_wildcard_match_check()
It's not entirely clear how to treat %NULL.
Clearly "match.interface-name=eth0" should not
match with an interface %NULL. But what about
"match.interface-name=!eth0"? It's now implemented
that negative matches still succeed against %NULL.
What about "match.interface-name=*"... | 0 | nm_wildcard_match_check(const char *str, const char *const *patterns, guint num_patterns)
{
gboolean has_optional = FALSE;
gboolean has_any_optional = FALSE;
guint i;
for (i = 0; i < num_patterns; i++) {
gboolean is_inverted;
gboolean is_mandatory;
gboolean match... | 141,536,908,928,198,920,000,000,000,000,000,000,000 | nm-core-utils.c | 185,298,728,942,567,930,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2021-20297 | A flaw was found in NetworkManager in versions before 1.30.0. Setting match.path and activating a profile crashes NetworkManager. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20297 |
206,678 | pdns | f9c57c98da1b1007a51680629b667d57d9b702b8 | https://github.com/PowerDNS/pdns | https://github.com/PowerDNS/pdns/commit/f9c57c98da1b1007a51680629b667d57d9b702b8 | dnsreplay: Bail out on a too small outgoing buffer | 1 | static void addECSOption(char* packet, const size_t& packetSize, uint16_t* len, const ComboAddress& remote, int stamp)
{
string EDNSRR;
struct dnsheader* dh = (struct dnsheader*) packet;
EDNSSubnetOpts eso;
if(stamp < 0)
eso.source = Netmask(remote);
else {
ComboAddress stamped(remote);
*((char*)... | 312,973,594,763,702,850,000,000,000,000,000,000,000 | dnsreplay.cc | 100,311,859,881,714,360,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-1046 | pdns before version 4.1.2 is vulnerable to a buffer overflow in dnsreplay. In the dnsreplay tool provided with PowerDNS Authoritative, replaying a specially crafted PCAP file can trigger a stack-based buffer overflow, leading to a crash and potentially arbitrary code execution. This buffer overflow only occurs when the... | https://nvd.nist.gov/vuln/detail/CVE-2018-1046 |
384,931 | pdns | f9c57c98da1b1007a51680629b667d57d9b702b8 | https://github.com/PowerDNS/pdns | https://github.com/PowerDNS/pdns/commit/f9c57c98da1b1007a51680629b667d57d9b702b8 | dnsreplay: Bail out on a too small outgoing buffer | 0 | static void addECSOption(char* packet, const size_t& packetSize, uint16_t* len, const ComboAddress& remote, int stamp)
{
string EDNSRR;
struct dnsheader* dh = (struct dnsheader*) packet;
EDNSSubnetOpts eso;
if(stamp < 0)
eso.source = Netmask(remote);
else {
ComboAddress stamped(remote);
*((char*)... | 287,127,598,791,815,800,000,000,000,000,000,000,000 | dnsreplay.cc | 86,630,863,213,211,260,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-1046 | pdns before version 4.1.2 is vulnerable to a buffer overflow in dnsreplay. In the dnsreplay tool provided with PowerDNS Authoritative, replaying a specially crafted PCAP file can trigger a stack-based buffer overflow, leading to a crash and potentially arbitrary code execution. This buffer overflow only occurs when the... | https://nvd.nist.gov/vuln/detail/CVE-2018-1046 |
206,681 | linux | ccd5b3235180eef3cfec337df1c8554ab151b5cc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ccd5b3235180eef3cfec337df1c8554ab151b5cc | x86/mm: Fix use-after-free of ldt_struct
The following commit:
39a0526fb3f7 ("x86/mm: Factor out LDT init from context init")
renamed init_new_context() to init_new_context_ldt() and added a new
init_new_context() which calls init_new_context_ldt(). However, the
error code of init_new_context_ldt() was ignored. ... | 1 | static inline int init_new_context(struct task_struct *tsk,
struct mm_struct *mm)
{
#ifdef CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS
if (cpu_feature_enabled(X86_FEATURE_OSPKE)) {
/* pkey 0 is the default and always allocated */
mm->context.pkey_allocation_map = 0x1;
/* -1 means unallocated or invalid */
... | 318,870,608,525,494,300,000,000,000,000,000,000,000 | mmu_context.h | 5,776,659,662,218,937,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-17053 | The init_new_context function in arch/x86/include/asm/mmu_context.h in the Linux kernel before 4.12.10 does not correctly handle errors from LDT table allocation when forking a new process, allowing a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted pro... | https://nvd.nist.gov/vuln/detail/CVE-2017-17053 |
384,972 | linux | ccd5b3235180eef3cfec337df1c8554ab151b5cc | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ccd5b3235180eef3cfec337df1c8554ab151b5cc | x86/mm: Fix use-after-free of ldt_struct
The following commit:
39a0526fb3f7 ("x86/mm: Factor out LDT init from context init")
renamed init_new_context() to init_new_context_ldt() and added a new
init_new_context() which calls init_new_context_ldt(). However, the
error code of init_new_context_ldt() was ignored. ... | 0 | static inline int init_new_context(struct task_struct *tsk,
struct mm_struct *mm)
{
#ifdef CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS
if (cpu_feature_enabled(X86_FEATURE_OSPKE)) {
/* pkey 0 is the default and always allocated */
mm->context.pkey_allocation_map = 0x1;
/* -1 means unallocated or invalid */
... | 141,782,712,450,043,970,000,000,000,000,000,000,000 | mmu_context.h | 309,536,435,937,687,370,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-17053 | The init_new_context function in arch/x86/include/asm/mmu_context.h in the Linux kernel before 4.12.10 does not correctly handle errors from LDT table allocation when forking a new process, allowing a local attacker to achieve a use-after-free or possibly have unspecified other impact by running a specially crafted pro... | https://nvd.nist.gov/vuln/detail/CVE-2017-17053 |
206,689 | qemu | 7a4ede0047a8613b0e3b72c9d351038f013dd357 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=7a4ede0047a8613b0e3b72c9d351038f013dd357 | audio/oss: fix buffer pos calculation
Fixes: 3ba4066d085f ("ossaudio: port to the new audio backend api")
Reported-by: ziming zhang <ezrakiez@gmail.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-Id: <20200120101804.29578-1-kraxel@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> | 1 | static size_t oss_write(HWVoiceOut *hw, void *buf, size_t len)
{
OSSVoiceOut *oss = (OSSVoiceOut *) hw;
size_t pos;
if (oss->mmapped) {
size_t total_len;
len = MIN(len, oss_get_available_bytes(oss));
total_len = len;
while (len) {
size_t to_copy = MIN(len, hw->s... | 320,577,837,338,217,500,000,000,000,000,000,000,000 | ossaudio.c | 56,102,907,344,443,710,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-14415 | oss_write in audio/ossaudio.c in QEMU before 5.0.0 mishandles a buffer position. | https://nvd.nist.gov/vuln/detail/CVE-2020-14415 |
385,124 | qemu | 7a4ede0047a8613b0e3b72c9d351038f013dd357 | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=7a4ede0047a8613b0e3b72c9d351038f013dd357 | audio/oss: fix buffer pos calculation
Fixes: 3ba4066d085f ("ossaudio: port to the new audio backend api")
Reported-by: ziming zhang <ezrakiez@gmail.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-Id: <20200120101804.29578-1-kraxel@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> | 0 | static size_t oss_write(HWVoiceOut *hw, void *buf, size_t len)
{
OSSVoiceOut *oss = (OSSVoiceOut *) hw;
size_t pos;
if (oss->mmapped) {
size_t total_len;
len = MIN(len, oss_get_available_bytes(oss));
total_len = len;
while (len) {
size_t to_copy = MIN(len, hw->s... | 41,964,730,168,801,900,000,000,000,000,000,000,000 | ossaudio.c | 197,354,221,101,911,800,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-14415 | oss_write in audio/ossaudio.c in QEMU before 5.0.0 mishandles a buffer position. | https://nvd.nist.gov/vuln/detail/CVE-2020-14415 |
206,690 | linux | fe9c842695e26d8116b61b80bfb905356f07834b | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe9c842695e26d8116b61b80bfb905356f07834b | NFC: llcp: Limit size of SDP URI
The tlv_len is u8, so we need to limit the size of the SDP URI. Enforce
this both in the NLA policy and in the code that performs the allocation
and copy, to avoid writing past the end of the allocated buffer.
Fixes: d9b8d8e19b073 ("NFC: llcp: Service Name Lookup netlink interface")
S... | 1 | struct nfc_llcp_sdp_tlv *nfc_llcp_build_sdreq_tlv(u8 tid, char *uri,
size_t uri_len)
{
struct nfc_llcp_sdp_tlv *sdreq;
pr_debug("uri: %s, len: %zu\n", uri, uri_len);
sdreq = kzalloc(sizeof(struct nfc_llcp_sdp_tlv), GFP_KERNEL);
if (sdreq == NULL)
return NULL;
sdreq->tlv_len = uri_len + 3;
if (uri[ur... | 260,858,063,612,082,200,000,000,000,000,000,000,000 | llcp_commands.c | 3,320,970,847,610,746,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-9518 | In nfc_llcp_build_sdreq_tlv of llcp_commands.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-7308... | https://nvd.nist.gov/vuln/detail/CVE-2018-9518 |
81,717 | linux | 58bdd544e2933a21a51eecf17c3f5f94038261b5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/58bdd544e2933a21a51eecf17c3f5f94038261b5 | net: nfc: Fix NULL dereference on nfc_llcp_build_tlv fails
KASAN report this:
BUG: KASAN: null-ptr-deref in nfc_llcp_build_gb+0x37f/0x540 [nfc]
Read of size 3 at addr 0000000000000000 by task syz-executor.0/5401
CPU: 0 PID: 5401 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45
Hardware name: QEMU Standard PC (i440FX ... | 0 | struct nfc_llcp_sdp_tlv *nfc_llcp_build_sdreq_tlv(u8 tid, char *uri,
size_t uri_len)
{
struct nfc_llcp_sdp_tlv *sdreq;
pr_debug("uri: %s, len: %zu\n", uri, uri_len);
/* sdreq->tlv_len is u8, takes uri_len, + 3 for header, + 1 for NULL */
if (WARN_ON_ONCE(uri_len > U8_MAX - 4))
return NULL;
sdreq = kza... | 184,918,844,048,432,000,000,000,000,000,000,000,000 | llcp_commands.c | 275,949,010,216,392,700,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-12818 | An issue was discovered in the Linux kernel before 4.20.15. The nfc_llcp_build_tlv function in net/nfc/llcp_commands.c may return NULL. If the caller does not check for this, it will trigger a NULL pointer dereference. This will cause denial of service. This affects nfc_llcp_build_gb in net/nfc/llcp_core.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12818 |
206,694 | linux | 7b55851367136b1efd84d98fea81ba57a98304cf | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b55851367136b1efd84d98fea81ba57a98304cf | fork: record start_time late
This changes the fork(2) syscall to record the process start_time after
initializing the basic task structure but still before making the new
process visible to user-space.
Technically, we could record the start_time anytime during fork(2). But
this might lead to scenarios where a start_... | 1 | static __latent_entropy struct task_struct *copy_process(
unsigned long clone_flags,
unsigned long stack_start,
unsigned long stack_size,
int __user *child_tidptr,
struct pid *pid,
int trace,
unsigned long tls,
int node)
{
int retval;
struct task_struct *p;
struct multiprocess... | 83,963,607,787,112,220,000,000,000,000,000,000,000 | fork.c | 67,424,250,209,851,440,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization decisions are improperly cached. This is related to lack of uid checking in polkitbackend/polkitbackendinteractiveauthority.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-6133 |
385,284 | linux | 7b55851367136b1efd84d98fea81ba57a98304cf | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b55851367136b1efd84d98fea81ba57a98304cf | fork: record start_time late
This changes the fork(2) syscall to record the process start_time after
initializing the basic task structure but still before making the new
process visible to user-space.
Technically, we could record the start_time anytime during fork(2). But
this might lead to scenarios where a start_... | 0 | static __latent_entropy struct task_struct *copy_process(
unsigned long clone_flags,
unsigned long stack_start,
unsigned long stack_size,
int __user *child_tidptr,
struct pid *pid,
int trace,
unsigned long tls,
int node)
{
int retval;
struct task_struct *p;
struct multiprocess... | 305,496,845,025,448,300,000,000,000,000,000,000,000 | fork.c | 314,817,395,960,866,500,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2019-6133 | In PolicyKit (aka polkit) 0.115, the "start time" protection mechanism can be bypassed because fork() is not atomic, and therefore authorization decisions are improperly cached. This is related to lack of uid checking in polkitbackend/polkitbackendinteractiveauthority.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-6133 |
206,719 | file | c0c0032b9e9eb57b91fefef905a3b018bab492d9 | https://github.com/file/file | https://github.com/glensc/file/commit/c0c0032b9e9eb57b91fefef905a3b018bab492d9 | Fix memory leak (Anatol Belski) | 1 |
private int
mget(struct magic_set *ms, const unsigned char *s, struct magic *m,
size_t nbytes, size_t o, unsigned int cont_level, int mode, int text,
int flip, int recursion_level, int *printed_something,
int *need_separator, int *returnval)
{
uint32_t soffset, offset = ms->offset;
uint32_t count = m->st... | 322,176,015,715,570,040,000,000,000,000,000,000,000 | softmagic.c | 102,587,707,711,526,050,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2014-1943 | Fine Free file before 5.17 allows context-dependent attackers to cause a denial of service (infinite recursion, CPU consumption, and crash) via a crafted indirect offset value in the magic of a file. | https://nvd.nist.gov/vuln/detail/CVE-2014-1943 |
385,786 | file | c0c0032b9e9eb57b91fefef905a3b018bab492d9 | https://github.com/file/file | https://github.com/glensc/file/commit/c0c0032b9e9eb57b91fefef905a3b018bab492d9 | Fix memory leak (Anatol Belski) | 0 |
private int
mget(struct magic_set *ms, const unsigned char *s, struct magic *m,
size_t nbytes, size_t o, unsigned int cont_level, int mode, int text,
int flip, int recursion_level, int *printed_something,
int *need_separator, int *returnval)
{
uint32_t soffset, offset = ms->offset;
uint32_t count = m->st... | 156,140,966,189,349,730,000,000,000,000,000,000,000 | softmagic.c | 44,336,109,592,356,870,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2014-1943 | Fine Free file before 5.17 allows context-dependent attackers to cause a denial of service (infinite recursion, CPU consumption, and crash) via a crafted indirect offset value in the magic of a file. | https://nvd.nist.gov/vuln/detail/CVE-2014-1943 |
206,724 | qemu | 8d1b247f3748ac4078524130c6d7ae42b6140aaf | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/8d1b247f3748ac4078524130c6d7ae42b6140aaf | vhost-vsock: detach the virqueue element in case of error
In vhost_vsock_common_send_transport_reset(), if an element popped from
the virtqueue is invalid, we should call virtqueue_detach_element() to
detach it from the virtqueue before freeing its memory.
Fixes: fc0b9b0e1c ("vhost-vsock: add virtio sockets device")
... | 1 | static void vhost_vsock_common_send_transport_reset(VHostVSockCommon *vvc)
{
VirtQueueElement *elem;
VirtQueue *vq = vvc->event_vq;
struct virtio_vsock_event event = {
.id = cpu_to_le32(VIRTIO_VSOCK_EVENT_TRANSPORT_RESET),
};
elem = virtqueue_pop(vq, sizeof(VirtQueueElement));
if (!elem... | 166,718,007,880,246,480,000,000,000,000,000,000,000 | vhost-vsock-common.c | 84,800,043,400,259,080,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2022-26354 | A flaw was found in the vhost-vsock device of QEMU. In case of error, an invalid element was not detached from the virtqueue before freeing its memory, leading to memory leakage and other unexpected results. Affected QEMU versions <= 6.2.0. | https://nvd.nist.gov/vuln/detail/CVE-2022-26354 |
385,956 | qemu | 8d1b247f3748ac4078524130c6d7ae42b6140aaf | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/8d1b247f3748ac4078524130c6d7ae42b6140aaf | vhost-vsock: detach the virqueue element in case of error
In vhost_vsock_common_send_transport_reset(), if an element popped from
the virtqueue is invalid, we should call virtqueue_detach_element() to
detach it from the virtqueue before freeing its memory.
Fixes: fc0b9b0e1c ("vhost-vsock: add virtio sockets device")
... | 0 | static void vhost_vsock_common_send_transport_reset(VHostVSockCommon *vvc)
{
VirtQueueElement *elem;
VirtQueue *vq = vvc->event_vq;
struct virtio_vsock_event event = {
.id = cpu_to_le32(VIRTIO_VSOCK_EVENT_TRANSPORT_RESET),
};
elem = virtqueue_pop(vq, sizeof(VirtQueueElement));
if (!elem... | 109,971,199,643,881,530,000,000,000,000,000,000,000 | vhost-vsock-common.c | 236,021,276,905,307,130,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2022-26354 | A flaw was found in the vhost-vsock device of QEMU. In case of error, an invalid element was not detached from the virtqueue before freeing its memory, leading to memory leakage and other unexpected results. Affected QEMU versions <= 6.2.0. | https://nvd.nist.gov/vuln/detail/CVE-2022-26354 |
206,773 | roundcubemail | 7c96646de0efda16cded8491138bfefe31aca940 | https://github.com/roundcube/roundcubemail | https://github.com/roundcube/roundcubemail/commit/7c96646de0efda16cded8491138bfefe31aca940 | Fix security issue in DBMail driver of password plugin (#1490261) | 1 | main(int argc, char *argv[])
{
int cnt,rc,cc;
char cmnd[255];
strcpy(cmnd, CMD);
if (argc > 1)
{
for (cnt = 1; cnt < argc; cnt++)
{
strcat(cmnd, " ");
strcat(cmnd, argv[cnt]);
}
}
else
{
fprintf(stderr, "__ %s: failed %d %d\n", argv[0], rc, cc);
return 255;
}
cc ... | 208,761,414,813,077,500,000,000,000,000,000,000,000 | chgdbmailusers.c | 235,401,159,063,232,400,000,000,000,000,000,000,000 | [
"CWE-74"
] | CVE-2015-2180 | The DBMail driver in the Password plugin in Roundcube before 1.1.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the password. | https://nvd.nist.gov/vuln/detail/CVE-2015-2180 |
386,607 | roundcubemail | 7c96646de0efda16cded8491138bfefe31aca940 | https://github.com/roundcube/roundcubemail | https://github.com/roundcube/roundcubemail/commit/7c96646de0efda16cded8491138bfefe31aca940 | Fix security issue in DBMail driver of password plugin (#1490261) | 0 | main(int argc, char *argv[])
{
int cnt,rc,cc;
char cmnd[1024];
strcpy(cmnd, CMD);
if (argc > 1)
{
for (cnt = 1; cnt < argc; cnt++)
{
strcat(cmnd, " ");
strcat(cmnd, argv[cnt]);
}
}
else
{
fprintf(stderr, "__ %s: failed %d %d\n", argv[0], rc, cc);
return 255;
}
cc... | 54,862,863,302,223,000,000,000,000,000,000,000,000 | chgdbmailusers.c | 129,396,682,276,445,400,000,000,000,000,000,000,000 | [
"CWE-74"
] | CVE-2015-2180 | The DBMail driver in the Password plugin in Roundcube before 1.1.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the password. | https://nvd.nist.gov/vuln/detail/CVE-2015-2180 |
206,775 | staging | 4c41aa24baa4ed338241d05494f2c595c885af8f | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?id=4c41aa24baa4ed338241d05494f2c595c885af8f | staging: ncpfs: memory corruption in ncp_read_kernel()
If the server is malicious then *bytes_read could be larger than the
size of the "target" buffer. It would lead to memory corruption when we
do the memcpy().
Reported-by: Dr Silvio Cesare of InfoSect <Silvio Cesare <silvio.cesare@gmail.com>
Signed-off-by: Dan Ca... | 1 | ncp_read_kernel(struct ncp_server *server, const char *file_id,
__u32 offset, __u16 to_read, char *target, int *bytes_read)
{
const char *source;
int result;
ncp_init_request(server);
ncp_add_byte(server, 0);
ncp_add_mem(server, file_id, 6);
ncp_add_be32(server, offset);
ncp_add_be16(server, to_read);
i... | 105,630,252,310,216,180,000,000,000,000,000,000,000 | ncplib_kernel.c | 92,999,281,510,421,150,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-8822 | Incorrect buffer length handling in the ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c in the Linux kernel through 4.15.11, and in drivers/staging/ncpfs/ncplib_kernel.c in the Linux kernel 4.16-rc through 4.16-rc6, could be exploited by malicious NCPFS servers to crash the kernel or execute code. | https://nvd.nist.gov/vuln/detail/CVE-2018-8822 |
386,644 | staging | 4c41aa24baa4ed338241d05494f2c595c885af8f | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging | https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?id=4c41aa24baa4ed338241d05494f2c595c885af8f | staging: ncpfs: memory corruption in ncp_read_kernel()
If the server is malicious then *bytes_read could be larger than the
size of the "target" buffer. It would lead to memory corruption when we
do the memcpy().
Reported-by: Dr Silvio Cesare of InfoSect <Silvio Cesare <silvio.cesare@gmail.com>
Signed-off-by: Dan Ca... | 0 | ncp_read_kernel(struct ncp_server *server, const char *file_id,
__u32 offset, __u16 to_read, char *target, int *bytes_read)
{
const char *source;
int result;
ncp_init_request(server);
ncp_add_byte(server, 0);
ncp_add_mem(server, file_id, 6);
ncp_add_be32(server, offset);
ncp_add_be16(server, to_read);
i... | 76,024,113,167,764,550,000,000,000,000,000,000,000 | ncplib_kernel.c | 261,046,370,665,278,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-8822 | Incorrect buffer length handling in the ncp_read_kernel function in fs/ncpfs/ncplib_kernel.c in the Linux kernel through 4.15.11, and in drivers/staging/ncpfs/ncplib_kernel.c in the Linux kernel 4.16-rc through 4.16-rc6, could be exploited by malicious NCPFS servers to crash the kernel or execute code. | https://nvd.nist.gov/vuln/detail/CVE-2018-8822 |
206,776 | ImageMagick | c5402b6e0fcf8b694ae2af6a6652ebb8ce0ccf46 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c5402b6e0fcf8b694ae2af6a6652ebb8ce0ccf46 | https://github.com/ImageMagick/ImageMagick/issues/717 | 1 | MagickExport Image *SampleImage(const Image *image,const size_t columns,
const size_t rows,ExceptionInfo *exception)
{
#define SampleImageTag "Sample/Image"
CacheView
*image_view,
*sample_view;
Image
*sample_image;
MagickBooleanType
status;
MagickOffsetType
progress;
register ssize... | 307,628,695,525,804,400,000,000,000,000,000,000,000 | resize.c | 69,078,255,384,331,350,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14248 | A heap-based buffer over-read in SampleImage() in MagickCore/resize.c in ImageMagick 7.0.6-8 Q16 allows remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14248 |
386,689 | ImageMagick | c5402b6e0fcf8b694ae2af6a6652ebb8ce0ccf46 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c5402b6e0fcf8b694ae2af6a6652ebb8ce0ccf46 | https://github.com/ImageMagick/ImageMagick/issues/717 | 0 | MagickExport Image *SampleImage(const Image *image,const size_t columns,
const size_t rows,ExceptionInfo *exception)
{
#define SampleImageTag "Sample/Image"
CacheView
*image_view,
*sample_view;
Image
*sample_image;
MagickBooleanType
status;
MagickOffsetType
progress;
register ssize... | 50,286,701,196,090,720,000,000,000,000,000,000,000 | resize.c | 140,366,744,473,706,350,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-14248 | A heap-based buffer over-read in SampleImage() in MagickCore/resize.c in ImageMagick 7.0.6-8 Q16 allows remote attackers to cause a denial of service via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-14248 |
206,778 | linux | e09463f220ca9a1a1ecfda84fcda658f99a1f12a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e09463f220ca9a1a1ecfda84fcda658f99a1f12a | jbd2: don't mark block as modified if the handle is out of credits
Do not set the b_modified flag in block's journal head should not
until after we're sure that jbd2_journal_dirty_metadat() will not
abort with an error due to there not being enough space reserved in
the jbd2 handle.
Otherwise, future attempts to modi... | 1 | int jbd2_journal_dirty_metadata(handle_t *handle, struct buffer_head *bh)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal;
struct journal_head *jh;
int ret = 0;
if (is_handle_aborted(handle))
return -EROFS;
if (!buffer_jbd(bh)) {
ret = -EUCLEAN;
goto out;
}
/*
* We don't grab j... | 170,042,211,051,181,890,000,000,000,000,000,000,000 | transaction.c | 297,192,259,061,206,230,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10883 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bounds write in jbd2_journal_dirty_metadata(), a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10883 |
386,732 | linux | e09463f220ca9a1a1ecfda84fcda658f99a1f12a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e09463f220ca9a1a1ecfda84fcda658f99a1f12a | jbd2: don't mark block as modified if the handle is out of credits
Do not set the b_modified flag in block's journal head should not
until after we're sure that jbd2_journal_dirty_metadat() will not
abort with an error due to there not being enough space reserved in
the jbd2 handle.
Otherwise, future attempts to modi... | 0 | int jbd2_journal_dirty_metadata(handle_t *handle, struct buffer_head *bh)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal;
struct journal_head *jh;
int ret = 0;
if (is_handle_aborted(handle))
return -EROFS;
if (!buffer_jbd(bh)) {
ret = -EUCLEAN;
goto out;
}
/*
* We don't grab j... | 58,372,101,817,151,770,000,000,000,000,000,000,000 | transaction.c | 87,541,004,333,327,500,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-10883 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause an out-of-bounds write in jbd2_journal_dirty_metadata(), a denial of service, and a system crash by mounting and operating on a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10883 |
206,779 | linux | 8b485ce69876c65db12ed390e7f9c0d2a64eff2c | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b485ce69876c65db12ed390e7f9c0d2a64eff2c | tcp: do not inherit fastopen_req from parent
Under fuzzer stress, it is possible that a child gets a non NULL
fastopen_req pointer from its parent at accept() time, when/if parent
morphs from listener to active session.
We need to make sure this can not happen, by clearing the field after
socket cloning.
BUG: Double... | 1 | struct sock *tcp_create_openreq_child(const struct sock *sk,
struct request_sock *req,
struct sk_buff *skb)
{
struct sock *newsk = inet_csk_clone_lock(sk, req, GFP_ATOMIC);
if (newsk) {
const struct inet_request_sock *ireq = inet_rsk(req);
struct tcp_request_sock *treq = tcp_rsk(req);
struc... | 300,954,496,186,608,960,000,000,000,000,000,000,000 | tcp_minisocks.c | 106,995,128,620,376,160,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-8890 | The inet_csk_clone_lock function in net/ipv4/inet_connection_sock.c in the Linux kernel through 4.10.15 allows attackers to cause a denial of service (double free) or possibly have unspecified other impact by leveraging use of the accept system call. | https://nvd.nist.gov/vuln/detail/CVE-2017-8890 |
386,742 | linux | 8b485ce69876c65db12ed390e7f9c0d2a64eff2c | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b485ce69876c65db12ed390e7f9c0d2a64eff2c | tcp: do not inherit fastopen_req from parent
Under fuzzer stress, it is possible that a child gets a non NULL
fastopen_req pointer from its parent at accept() time, when/if parent
morphs from listener to active session.
We need to make sure this can not happen, by clearing the field after
socket cloning.
BUG: Double... | 0 | struct sock *tcp_create_openreq_child(const struct sock *sk,
struct request_sock *req,
struct sk_buff *skb)
{
struct sock *newsk = inet_csk_clone_lock(sk, req, GFP_ATOMIC);
if (newsk) {
const struct inet_request_sock *ireq = inet_rsk(req);
struct tcp_request_sock *treq = tcp_rsk(req);
struc... | 321,355,660,008,835,140,000,000,000,000,000,000,000 | tcp_minisocks.c | 35,355,767,680,306,774,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-8890 | The inet_csk_clone_lock function in net/ipv4/inet_connection_sock.c in the Linux kernel through 4.10.15 allows attackers to cause a denial of service (double free) or possibly have unspecified other impact by leveraging use of the accept system call. | https://nvd.nist.gov/vuln/detail/CVE-2017-8890 |
206,783 | libslirp | 68ccb8021a838066f0951d4b2817eb6b6f10a843 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843 | tcp_emu: fix unsafe snprintf() usages
Various calls to snprintf() assume that snprintf() returns "only" the
number of bytes written (excluding terminating NUL).
https://pubs.opengroup.org/onlinepubs/9699919799/functions/snprintf.html#tag_16_159_04
"Upon successful completion, the snprintf() function shall return the... | 1 | int tcp_emu(struct socket *so, struct mbuf *m)
{
Slirp *slirp = so->slirp;
unsigned n1, n2, n3, n4, n5, n6;
char buff[257];
uint32_t laddr;
unsigned lport;
char *bptr;
DEBUG_CALL("tcp_emu");
DEBUG_ARG("so = %p", so);
DEBUG_ARG("m = %p", m);
switch (so->so_emu) {
int x, ... | 160,002,586,061,213,930,000,000,000,000,000,000,000 | tcp_subr.c | 169,113,495,507,406,880,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-8608 | In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code. | https://nvd.nist.gov/vuln/detail/CVE-2020-8608 |
386,772 | libslirp | 68ccb8021a838066f0951d4b2817eb6b6f10a843 | https://gitlab.freedesktop.org/slirp/libslirp | https://gitlab.freedesktop.org/slirp/libslirp/commit/68ccb8021a838066f0951d4b2817eb6b6f10a843 | tcp_emu: fix unsafe snprintf() usages
Various calls to snprintf() assume that snprintf() returns "only" the
number of bytes written (excluding terminating NUL).
https://pubs.opengroup.org/onlinepubs/9699919799/functions/snprintf.html#tag_16_159_04
"Upon successful completion, the snprintf() function shall return the... | 0 | int tcp_emu(struct socket *so, struct mbuf *m)
{
Slirp *slirp = so->slirp;
unsigned n1, n2, n3, n4, n5, n6;
char buff[257];
uint32_t laddr;
unsigned lport;
char *bptr;
DEBUG_CALL("tcp_emu");
DEBUG_ARG("so = %p", so);
DEBUG_ARG("m = %p", m);
switch (so->so_emu) {
int x, ... | 193,279,267,261,084,830,000,000,000,000,000,000,000 | tcp_subr.c | 174,553,630,285,571,150,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-8608 | In libslirp 4.1.0, as used in QEMU 4.2.0, tcp_subr.c misuses snprintf return values, leading to a buffer overflow in later code. | https://nvd.nist.gov/vuln/detail/CVE-2020-8608 |
206,784 | libplist | 4765d9a60ca4248a8f89289271ac69cbffcc29bc | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/4765d9a60ca4248a8f89289271ac69cbffcc29bc | bplist: Fix possible out-of-bounds read in parse_array_node() with proper bounds checking | 1 | static plist_t parse_array_node(struct bplist_data *bplist, const char** bnode, uint64_t size)
{
uint64_t j;
uint32_t str_j = 0;
uint32_t index1;
plist_data_t data = plist_new_plist_data();
data->type = PLIST_ARRAY;
data->length = size;
plist_t node = node_create(NULL, data);
for (j ... | 27,588,535,501,992,160,000,000,000,000,000,000,000 | bplist.c | 267,128,716,589,674,740,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-5834 | The parse_dict_node function in bplist.c in libplist allows attackers to cause a denial of service (out-of-bounds heap read and crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5834 |
386,790 | libplist | 4765d9a60ca4248a8f89289271ac69cbffcc29bc | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/4765d9a60ca4248a8f89289271ac69cbffcc29bc | bplist: Fix possible out-of-bounds read in parse_array_node() with proper bounds checking | 0 | static plist_t parse_array_node(struct bplist_data *bplist, const char** bnode, uint64_t size)
{
uint64_t j;
uint64_t str_j = 0;
uint64_t index1;
plist_data_t data = plist_new_plist_data();
const char *const end_data = bplist->data + bplist->size;
const char *index1_ptr = NULL;
data->type =... | 201,503,186,607,211,800,000,000,000,000,000,000,000 | bplist.c | 181,407,497,137,739,640,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-5834 | The parse_dict_node function in bplist.c in libplist allows attackers to cause a denial of service (out-of-bounds heap read and crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-5834 |
206,785 | libvpx | 45daecb4f73a47ab3236a29a3a48c52324cbf19a | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/45daecb4f73a47ab3236a29a3a48c52324cbf19a | vp8_decode_frame: fix oob read on truncated key frame
the check for error correction being disabled was overriding the data
length checks. this avoids returning incorrect information (width /
height) for the decoded frame which could result in inconsistent sizes
returned in to an application causing it to read beyond ... | 1 | int vp8_decode_frame(VP8D_COMP *pbi) {
vp8_reader *const bc = &pbi->mbc[8];
VP8_COMMON *const pc = &pbi->common;
MACROBLOCKD *const xd = &pbi->mb;
const unsigned char *data = pbi->fragments.ptrs[0];
const unsigned int data_sz = pbi->fragments.sizes[0];
const unsigned char *data_end = data + data_sz;
ptrdi... | 59,365,551,834,124,920,000,000,000,000,000,000,000 | decodeframe.c | 275,398,118,260,246,260,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-0034 | In vp8_decode_frame of decodeframe.c, there is a possible out of bounds read due to improper input validation. This could lead to remote information disclosure if error correction were turned on, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: An... | https://nvd.nist.gov/vuln/detail/CVE-2020-0034 |
386,801 | libvpx | 45daecb4f73a47ab3236a29a3a48c52324cbf19a | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/45daecb4f73a47ab3236a29a3a48c52324cbf19a | vp8_decode_frame: fix oob read on truncated key frame
the check for error correction being disabled was overriding the data
length checks. this avoids returning incorrect information (width /
height) for the decoded frame which could result in inconsistent sizes
returned in to an application causing it to read beyond ... | 0 | int vp8_decode_frame(VP8D_COMP *pbi) {
vp8_reader *const bc = &pbi->mbc[8];
VP8_COMMON *const pc = &pbi->common;
MACROBLOCKD *const xd = &pbi->mb;
const unsigned char *data = pbi->fragments.ptrs[0];
const unsigned int data_sz = pbi->fragments.sizes[0];
const unsigned char *data_end = data + data_sz;
ptrdi... | 184,940,009,001,815,800,000,000,000,000,000,000,000 | decodeframe.c | 113,230,693,734,728,500,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-0034 | In vp8_decode_frame of decodeframe.c, there is a possible out of bounds read due to improper input validation. This could lead to remote information disclosure if error correction were turned on, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: An... | https://nvd.nist.gov/vuln/detail/CVE-2020-0034 |
206,786 | tor | 602dcd8e3774b09242787ba3b0f0e0599530638a | https://github.com/torproject/tor | https://gitlab.torproject.org/tpo/core/tor/-/commit/602dcd8e3774b09242787ba3b0f0e0599530638a | hs-v2: Only log once the connection warning to v2
Closes #40474
Signed-off-by: David Goulet <dgoulet@torproject.org> | 1 | connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
origin_circuit_t *circ,
crypt_path_t *cpath)
{
socks_request_t *socks = conn->socks_request;
const or_options_t *options = get_options();
connection_t *base_co... | 219,182,903,095,322,250,000,000,000,000,000,000,000 | connection_edge.c | 143,028,968,066,812,720,000,000,000,000,000,000,000 | [
"CWE-532"
] | CVE-2021-22929 | An information disclosure exists in Brave Browser Desktop prior to version 1.28.62, where logged warning messages that included timestamps of connections to V2 onion domains in tor.log. | https://nvd.nist.gov/vuln/detail/CVE-2021-22929 |
386,808 | tor | 602dcd8e3774b09242787ba3b0f0e0599530638a | https://github.com/torproject/tor | https://gitlab.torproject.org/tpo/core/tor/-/commit/602dcd8e3774b09242787ba3b0f0e0599530638a | hs-v2: Only log once the connection warning to v2
Closes #40474
Signed-off-by: David Goulet <dgoulet@torproject.org> | 0 | connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
origin_circuit_t *circ,
crypt_path_t *cpath)
{
socks_request_t *socks = conn->socks_request;
const or_options_t *options = get_options();
connection_t *base_co... | 144,004,765,748,378,210,000,000,000,000,000,000,000 | connection_edge.c | 139,216,366,318,724,800,000,000,000,000,000,000,000 | [
"CWE-532"
] | CVE-2021-22929 | An information disclosure exists in Brave Browser Desktop prior to version 1.28.62, where logged warning messages that included timestamps of connections to V2 onion domains in tor.log. | https://nvd.nist.gov/vuln/detail/CVE-2021-22929 |
206,787 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 1 | static UINT serial_process_irp_write(SERIAL_DEVICE* serial, IRP* irp)
{
UINT32 Length;
UINT64 Offset;
DWORD nbWritten = 0;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UINT32(irp->input, Length); /* Length (4 bytes) */
Stream_Read_UINT64(irp->input, Offset); /* Offset... | 171,086,284,749,578,300,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
386,963 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 0 | static UINT serial_process_irp_write(SERIAL_DEVICE* serial, IRP* irp)
{
UINT32 Length;
UINT64 Offset;
void* ptr;
DWORD nbWritten = 0;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UINT32(irp->input, Length); /* Length (4 bytes) */
Stream_Read_UINT64(irp->input, Offset... | 201,286,241,341,962,450,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
206,790 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 1 | static UINT rdpei_recv_pdu(RDPEI_CHANNEL_CALLBACK* callback, wStream* s)
{
UINT16 eventId;
UINT32 pduLength;
UINT error;
Stream_Read_UINT16(s, eventId); /* eventId (2 bytes) */
Stream_Read_UINT32(s, pduLength); /* pduLength (4 bytes) */
#ifdef WITH_DEBUG_RDPEI
WLog_DBG(TAG, "rdpei_recv_pdu: eventId: %" PRIu16 "... | 226,022,866,761,581,500,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
386,915 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 0 | static UINT rdpei_recv_pdu(RDPEI_CHANNEL_CALLBACK* callback, wStream* s)
{
UINT16 eventId;
UINT32 pduLength;
UINT error;
if (Stream_GetRemainingLength(s) < 6)
return ERROR_INVALID_DATA;
Stream_Read_UINT16(s, eventId); /* eventId (2 bytes) */
Stream_Read_UINT32(s, pduLength); /* pduLength (4 bytes) */
#ifdef ... | 253,183,286,498,688,000,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
206,792 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 1 | static UINT printer_process_irp_write(PRINTER_DEVICE* printer_dev, IRP* irp)
{
UINT32 Length;
UINT64 Offset;
rdpPrintJob* printjob = NULL;
UINT error = CHANNEL_RC_OK;
Stream_Read_UINT32(irp->input, Length);
Stream_Read_UINT64(irp->input, Offset);
Stream_Seek(irp->input, 20); /* Padding */
if (printer_dev->prin... | 246,063,967,523,581,560,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
386,886 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 0 | static UINT printer_process_irp_write(PRINTER_DEVICE* printer_dev, IRP* irp)
{
UINT32 Length;
UINT64 Offset;
rdpPrintJob* printjob = NULL;
UINT error = CHANNEL_RC_OK;
void* ptr;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UINT32(irp->input, Length);
Stream_Read_UINT... | 295,673,703,644,796,030,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
206,795 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 1 | static UINT serial_process_irp_create(SERIAL_DEVICE* serial, IRP* irp)
{
DWORD DesiredAccess;
DWORD SharedAccess;
DWORD CreateDisposition;
UINT32 PathLength;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UINT32(irp->input, DesiredAccess); /* DesiredAccess (4 bytes)... | 22,984,095,021,020,594,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
386,955 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 0 | static UINT serial_process_irp_create(SERIAL_DEVICE* serial, IRP* irp)
{
DWORD DesiredAccess;
DWORD SharedAccess;
DWORD CreateDisposition;
UINT32 PathLength;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UINT32(irp->input, DesiredAccess); /* DesiredAccess (4 bytes)... | 249,612,370,891,325,340,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
206,797 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 1 | static UINT drive_process_irp_write(DRIVE_DEVICE* drive, IRP* irp)
{
DRIVE_FILE* file;
UINT32 Length;
UINT64 Offset;
if (!drive || !irp || !irp->input || !irp->output || !irp->Complete)
return ERROR_INVALID_PARAMETER;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
Stream_Read_UI... | 135,919,772,905,875,170,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
386,873 | FreeRDP | 6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | https://github.com/FreeRDP/FreeRDP | https://github.com/FreeRDP/FreeRDP/commit/6b485b146a1b9d6ce72dfd7b5f36456c166e7a16 | Fixed oob read in irp_write and similar | 0 | static UINT drive_process_irp_write(DRIVE_DEVICE* drive, IRP* irp)
{
DRIVE_FILE* file;
UINT32 Length;
UINT64 Offset;
void* ptr;
if (!drive || !irp || !irp->input || !irp->output || !irp->Complete)
return ERROR_INVALID_PARAMETER;
if (Stream_GetRemainingLength(irp->input) < 32)
return ERROR_INVALID_DATA;
St... | 331,242,947,960,249,450,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2020-11089 | In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0. | https://nvd.nist.gov/vuln/detail/CVE-2020-11089 |
206,813 | newsbeuter | 26f5a4350f3ab5507bb8727051c87bb04660f333 | https://github.com/akrennmair/newsbeuter | https://github.com/akrennmair/newsbeuter/commit/26f5a4350f3ab5507bb8727051c87bb04660f333 | Work around shell code in podcast names (#598) | 1 | std::string queueloader::get_filename(const std::string& str) {
std::string fn = ctrl->get_dlpath();
if (fn[fn.length()-1] != NEWSBEUTER_PATH_SEP[0])
fn.append(NEWSBEUTER_PATH_SEP);
char buf[1024];
snprintf(buf, sizeof(buf), "%s", str.c_str());
char * base = basename(buf);
if (!base || strlen(base) == 0) {
c... | 266,088,374,115,299,070,000,000,000,000,000,000,000 | queueloader.cpp | 226,567,759,103,813,970,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-14500 | Improper Neutralization of Special Elements used in an OS Command in the podcast playback function of Podbeuter in Newsbeuter 0.3 through 2.9 allows remote attackers to perform user-assisted code execution by crafting an RSS item with a media enclosure (i.e., a podcast file) that includes shell metacharacters in its fi... | https://nvd.nist.gov/vuln/detail/CVE-2017-14500 |
387,144 | newsbeuter | 26f5a4350f3ab5507bb8727051c87bb04660f333 | https://github.com/akrennmair/newsbeuter | https://github.com/akrennmair/newsbeuter/commit/26f5a4350f3ab5507bb8727051c87bb04660f333 | Work around shell code in podcast names (#598) | 0 | std::string queueloader::get_filename(const std::string& str) {
std::string fn = ctrl->get_dlpath();
if (fn[fn.length()-1] != NEWSBEUTER_PATH_SEP[0])
fn.append(NEWSBEUTER_PATH_SEP);
char buf[1024];
snprintf(buf, sizeof(buf), "%s", str.c_str());
char * base = basename(buf);
if (!base || strlen(base) == 0) {
c... | 120,600,818,775,828,650,000,000,000,000,000,000,000 | queueloader.cpp | 207,159,011,548,898,300,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-14500 | Improper Neutralization of Special Elements used in an OS Command in the podcast playback function of Podbeuter in Newsbeuter 0.3 through 2.9 allows remote attackers to perform user-assisted code execution by crafting an RSS item with a media enclosure (i.e., a podcast file) that includes shell metacharacters in its fi... | https://nvd.nist.gov/vuln/detail/CVE-2017-14500 |
206,814 | newsbeuter | 26f5a4350f3ab5507bb8727051c87bb04660f333 | https://github.com/akrennmair/newsbeuter | https://github.com/akrennmair/newsbeuter/commit/26f5a4350f3ab5507bb8727051c87bb04660f333 | Work around shell code in podcast names (#598) | 1 | void pb_controller::play_file(const std::string& file) {
std::string cmdline;
std::string player = cfg->get_configvalue("player");
if (player == "")
return;
cmdline.append(player);
cmdline.append(" \"");
cmdline.append(utils::replace_all(file,"\"", "\\\""));
cmdline.append("\"");
stfl::reset();
LOG(LOG_DEBUG... | 184,264,805,643,092,050,000,000,000,000,000,000,000 | pb_controller.cpp | 57,156,306,193,178,130,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-14500 | Improper Neutralization of Special Elements used in an OS Command in the podcast playback function of Podbeuter in Newsbeuter 0.3 through 2.9 allows remote attackers to perform user-assisted code execution by crafting an RSS item with a media enclosure (i.e., a podcast file) that includes shell metacharacters in its fi... | https://nvd.nist.gov/vuln/detail/CVE-2017-14500 |
387,148 | newsbeuter | 26f5a4350f3ab5507bb8727051c87bb04660f333 | https://github.com/akrennmair/newsbeuter | https://github.com/akrennmair/newsbeuter/commit/26f5a4350f3ab5507bb8727051c87bb04660f333 | Work around shell code in podcast names (#598) | 0 | void pb_controller::play_file(const std::string& file) {
std::string cmdline;
std::string player = cfg->get_configvalue("player");
if (player == "")
return;
cmdline.append(player);
cmdline.append(" \'");
cmdline.append(utils::replace_all(file,"'", "%27"));
cmdline.append("\'");
stfl::reset();
LOG(LOG_DEBUG, ... | 18,228,994,528,375,457,000,000,000,000,000,000,000 | pb_controller.cpp | 96,554,928,575,293,530,000,000,000,000,000,000,000 | [
"CWE-78"
] | CVE-2017-14500 | Improper Neutralization of Special Elements used in an OS Command in the podcast playback function of Podbeuter in Newsbeuter 0.3 through 2.9 allows remote attackers to perform user-assisted code execution by crafting an RSS item with a media enclosure (i.e., a podcast file) that includes shell metacharacters in its fi... | https://nvd.nist.gov/vuln/detail/CVE-2017-14500 |
206,816 | dbus | 47b1a4c41004bf494b87370987b222c934b19016 | http://gitweb.freedesktop.org/?p=dbus/dbus | https://gitlab.freedesktop.org/dbus/dbus/commit/47b1a4c41004bf494b87370987b222c934b19016 | auth: Reject DBUS_COOKIE_SHA1 for users other than the server owner
The DBUS_COOKIE_SHA1 authentication mechanism aims to prove ownership
of a shared home directory by having the server write a secret "cookie"
into a .dbus-keyrings subdirectory of the desired identity's home
directory with 0700 permissions, and having... | 1 | sha1_handle_first_client_response (DBusAuth *auth,
const DBusString *data)
{
/* We haven't sent a challenge yet, we're expecting a desired
* username from the client.
*/
DBusString tmp;
DBusString tmp2;
dbus_bool_t retval = FALSE;
DBusError error = DBUS_ERROR_I... | 190,285,309,042,191,900,000,000,000,000,000,000,000 | dbus-auth.c | 137,711,122,611,578,580,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2019-12749 | dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only ... | https://nvd.nist.gov/vuln/detail/CVE-2019-12749 |
387,182 | dbus | 47b1a4c41004bf494b87370987b222c934b19016 | http://gitweb.freedesktop.org/?p=dbus/dbus | https://gitlab.freedesktop.org/dbus/dbus/commit/47b1a4c41004bf494b87370987b222c934b19016 | auth: Reject DBUS_COOKIE_SHA1 for users other than the server owner
The DBUS_COOKIE_SHA1 authentication mechanism aims to prove ownership
of a shared home directory by having the server write a secret "cookie"
into a .dbus-keyrings subdirectory of the desired identity's home
directory with 0700 permissions, and having... | 0 | sha1_handle_first_client_response (DBusAuth *auth,
const DBusString *data)
{
/* We haven't sent a challenge yet, we're expecting a desired
* username from the client.
*/
DBusString tmp;
DBusString tmp2;
dbus_bool_t retval = FALSE;
DBusError error = DBUS_ERROR_I... | 83,543,845,176,161,310,000,000,000,000,000,000,000 | dbus-auth.c | 113,463,513,614,785,550,000,000,000,000,000,000,000 | [
"CWE-59"
] | CVE-2019-12749 | dbus before 1.10.28, 1.12.x before 1.12.16, and 1.13.x before 1.13.12, as used in DBusServer in Canonical Upstart in Ubuntu 14.04 (and in some, less common, uses of dbus-daemon), allows cookie spoofing because of symlink mishandling in the reference implementation of DBUS_COOKIE_SHA1 in the libdbus library. (This only ... | https://nvd.nist.gov/vuln/detail/CVE-2019-12749 |
206,824 | exiv2 | 6e42c1b55e0fc4f360cc56010b0ffe19aa6062d9 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/6e42c1b55e0fc4f360cc56010b0ffe19aa6062d9 | Fix #561. Use proper counter for the idx variable | 1 | ExifData::const_iterator isoSpeed(const ExifData& ed)
{
static const char* keys[] = {
"Exif.Photo.ISOSpeedRatings",
"Exif.Image.ISOSpeedRatings",
"Exif.CanonSi.ISOSpeed",
"Exif.CanonCs.ISOSpeed",
"Exif.Nikon1.ISOSpeed",
"Exif.Nikon2... | 159,683,510,631,697,760,000,000,000,000,000,000,000 | easyaccess.cpp | 187,587,578,520,024,860,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-19607 | Exiv2::isoSpeed in easyaccess.cpp in Exiv2 v0.27-RC2 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-19607 |
387,281 | exiv2 | 6e42c1b55e0fc4f360cc56010b0ffe19aa6062d9 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/6e42c1b55e0fc4f360cc56010b0ffe19aa6062d9 | Fix #561. Use proper counter for the idx variable | 0 | ExifData::const_iterator isoSpeed(const ExifData& ed)
{
static const char* keys[] = {
"Exif.Photo.ISOSpeedRatings",
"Exif.Image.ISOSpeedRatings",
"Exif.CanonSi.ISOSpeed",
"Exif.CanonCs.ISOSpeed",
"Exif.Nikon1.ISOSpeed",
"Exif.Nikon2... | 278,955,642,591,743,570,000,000,000,000,000,000,000 | easyaccess.cpp | 96,978,696,680,076,620,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-19607 | Exiv2::isoSpeed in easyaccess.cpp in Exiv2 v0.27-RC2 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-19607 |
206,825 | systemd | 052c57f132f04a3cf4148f87561618da1a6908b4 | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/052c57f132f04a3cf4148f87561618da1a6908b4 | journald: set a limit on the number of fields (1k)
We allocate a iovec entry for each field, so with many short entries,
our memory usage and processing time can be large, even with a relatively
small message size. Let's refuse overly long entries.
CVE-2018-16865
https://bugzilla.redhat.com/show_bug.cgi?id=1653861
W... | 1 | static int server_process_entry(
Server *s,
const void *buffer, size_t *remaining,
ClientContext *context,
const struct ucred *ucred,
const struct timeval *tv,
const char *label, size_t label_len) {
/* Process a sin... | 269,979,507,634,530,270,000,000,000,000,000,000,000 | journald-native.c | 316,796,261,928,753,120,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2018-16865 | An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute cod... | https://nvd.nist.gov/vuln/detail/CVE-2018-16865 |
387,290 | systemd | 052c57f132f04a3cf4148f87561618da1a6908b4 | https://github.com/systemd/systemd | https://github.com/systemd/systemd/commit/052c57f132f04a3cf4148f87561618da1a6908b4 | journald: set a limit on the number of fields (1k)
We allocate a iovec entry for each field, so with many short entries,
our memory usage and processing time can be large, even with a relatively
small message size. Let's refuse overly long entries.
CVE-2018-16865
https://bugzilla.redhat.com/show_bug.cgi?id=1653861
W... | 0 | static int server_process_entry(
Server *s,
const void *buffer, size_t *remaining,
ClientContext *context,
const struct ucred *ucred,
const struct timeval *tv,
const char *label, size_t label_len) {
/* Process a sin... | 244,316,526,945,396,050,000,000,000,000,000,000,000 | journald-native.c | 325,850,447,366,401,400,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2018-16865 | An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the journal socket. A local attacker, or a remote one if systemd-journal-remote is used, may use this flaw to crash systemd-journald or execute cod... | https://nvd.nist.gov/vuln/detail/CVE-2018-16865 |
206,826 | openldap | 6abfd60078af02d56edb3b6897692cdd09a08971 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/6abfd60078af02d56edb3b6897692cdd09a08971 | ITS#9370 revert previous commit, alternate fix
Just skip normalization if there's no equality rule. We accept
DNs without equality rules already. | 1 | slap_modrdn2mods(
Operation *op,
SlapReply *rs )
{
int a_cnt, d_cnt;
LDAPRDN old_rdn = NULL;
LDAPRDN new_rdn = NULL;
assert( !BER_BVISEMPTY( &op->oq_modrdn.rs_newrdn ) );
/* if requestDN is empty, silently reset deleteOldRDN */
if ( BER_BVISEMPTY( &op->o_req_dn ) ) op->orr_deleteoldrdn = 0;
if ( ldap_bv2... | 135,780,004,756,843,210,000,000,000,000,000,000,000 | modrdn.c | 231,223,681,146,545,050,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2020-25692 | A NULL pointer dereference was found in OpenLDAP server and was fixed in openldap 2.4.55, during a request for renaming RDNs. An unauthenticated attacker could remotely crash the slapd process by sending a specially crafted request, causing a Denial of Service. | https://nvd.nist.gov/vuln/detail/CVE-2020-25692 |
387,296 | openldap | 6abfd60078af02d56edb3b6897692cdd09a08971 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/6abfd60078af02d56edb3b6897692cdd09a08971 | ITS#9370 revert previous commit, alternate fix
Just skip normalization if there's no equality rule. We accept
DNs without equality rules already. | 0 | slap_modrdn2mods(
Operation *op,
SlapReply *rs )
{
int a_cnt, d_cnt;
LDAPRDN old_rdn = NULL;
LDAPRDN new_rdn = NULL;
assert( !BER_BVISEMPTY( &op->oq_modrdn.rs_newrdn ) );
/* if requestDN is empty, silently reset deleteOldRDN */
if ( BER_BVISEMPTY( &op->o_req_dn ) ) op->orr_deleteoldrdn = 0;
if ( ldap_bv2... | 82,662,295,129,122,760,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-25692 | A NULL pointer dereference was found in OpenLDAP server and was fixed in openldap 2.4.55, during a request for renaming RDNs. An unauthenticated attacker could remotely crash the slapd process by sending a specially crafted request, causing a Denial of Service. | https://nvd.nist.gov/vuln/detail/CVE-2020-25692 |
206,828 | linux | b86dab054059b970111b5516ae548efaae5b3aae | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b86dab054059b970111b5516ae548efaae5b3aae | vt: keyboard: avoid signed integer overflow in k_ascii
When k_ascii is invoked several times in a row there is a potential for
signed integer overflow:
UBSAN: Undefined behaviour in drivers/tty/vt/keyboard.c:888:19 signed integer overflow:
10 * 1111111111 cannot be represented in type 'int'
CPU: 0 PID: 0 Comm: swappe... | 1 | static void k_ascii(struct vc_data *vc, unsigned char value, char up_flag)
{
int base;
if (up_flag)
return;
if (value < 10) {
/* decimal input of code, while Alt depressed */
base = 10;
} else {
/* hexadecimal input of code, while AltGr depressed */
value -= 10;
base = 16;
}
if (npadch == -1)
npa... | 257,694,823,537,430,400,000,000,000,000,000,000,000 | keyboard.c | 325,168,745,266,816,040,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-13974 | An issue was discovered in the Linux kernel 4.4 through 5.7.1. drivers/tty/vt/keyboard.c has an integer overflow if k_ascii is called several times in a row, aka CID-b86dab054059. NOTE: Members in the community argue that the integer overflow does not lead to a security issue in this case. | https://nvd.nist.gov/vuln/detail/CVE-2020-13974 |
387,381 | linux | b86dab054059b970111b5516ae548efaae5b3aae | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b86dab054059b970111b5516ae548efaae5b3aae | vt: keyboard: avoid signed integer overflow in k_ascii
When k_ascii is invoked several times in a row there is a potential for
signed integer overflow:
UBSAN: Undefined behaviour in drivers/tty/vt/keyboard.c:888:19 signed integer overflow:
10 * 1111111111 cannot be represented in type 'int'
CPU: 0 PID: 0 Comm: swappe... | 0 | static void k_ascii(struct vc_data *vc, unsigned char value, char up_flag)
{
unsigned int base;
if (up_flag)
return;
if (value < 10) {
/* decimal input of code, while Alt depressed */
base = 10;
} else {
/* hexadecimal input of code, while AltGr depressed */
value -= 10;
base = 16;
}
if (!npadch_ac... | 281,450,362,659,703,480,000,000,000,000,000,000,000 | keyboard.c | 147,055,318,206,568,610,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2020-13974 | An issue was discovered in the Linux kernel 4.4 through 5.7.1. drivers/tty/vt/keyboard.c has an integer overflow if k_ascii is called several times in a row, aka CID-b86dab054059. NOTE: Members in the community argue that the integer overflow does not lead to a security issue in this case. | https://nvd.nist.gov/vuln/detail/CVE-2020-13974 |
206,830 | libass | 017137471d0043e0321e377ed8da48e45a3ec632 | https://github.com/libass/libass | https://github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e45a3ec632 | decode_font: fix subtraction broken by change to unsigned type
This caused a one-byte buffer overwrite and an assertion failure.
Regression in commit 910211f1c0078e37546f73e95306724358b89be2.
Discovered by OSS-Fuzz.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674.
Fixes https://bugs.chromium.org/p... | 1 | static int decode_font(ASS_Track *track)
{
unsigned char *p;
unsigned char *q;
size_t i;
size_t size; // original size
size_t dsize; // decoded size
unsigned char *buf = 0;
ass_msg(track->library, MSGL_V, "Font: %d bytes encoded data",
track->p... | 16,493,980,437,284,498,000,000,000,000,000,000,000 | ass.c | 167,296,279,316,371,390,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-36430 | libass 0.15.x before 0.15.1 has a heap-based buffer overflow in decode_chars (called from decode_font and process_text) because the wrong integer data type is used for subtraction. | https://nvd.nist.gov/vuln/detail/CVE-2020-36430 |
387,404 | libass | 017137471d0043e0321e377ed8da48e45a3ec632 | https://github.com/libass/libass | https://github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e45a3ec632 | decode_font: fix subtraction broken by change to unsigned type
This caused a one-byte buffer overwrite and an assertion failure.
Regression in commit 910211f1c0078e37546f73e95306724358b89be2.
Discovered by OSS-Fuzz.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674.
Fixes https://bugs.chromium.org/p... | 0 | static int decode_font(ASS_Track *track)
{
unsigned char *p;
unsigned char *q;
size_t i;
size_t size; // original size
size_t dsize; // decoded size
unsigned char *buf = 0;
ass_msg(track->library, MSGL_V, "Font: %d bytes encoded data",
track->p... | 37,409,588,686,926,230,000,000,000,000,000,000,000 | ass.c | 216,829,813,896,281,960,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2020-36430 | libass 0.15.x before 0.15.1 has a heap-based buffer overflow in decode_chars (called from decode_font and process_text) because the wrong integer data type is used for subtraction. | https://nvd.nist.gov/vuln/detail/CVE-2020-36430 |
206,839 | gdal | 767e3a56144f676ca738ef8f700e0e56035bd05a | https://github.com/OSGeo/gdal | https://github.com/OSGeo/gdal/commit/767e3a56144f676ca738ef8f700e0e56035bd05a | netCDF: avoid buffer overflow. master only. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15143. Credit to OSS Fuzz | 1 | std::string& attrf(int ncid, int varId, const char * attrName, std::string& alloc)
{
alloc = "";
size_t len = 0;
nc_inq_attlen(ncid, varId, attrName, &len);
if(len < 1)
{
return alloc;
}
char attr_vals[NC_MAX_NAME + 1];
memse... | 279,575,261,817,016,860,000,000,000,000,000,000,000 | netcdfsg.cpp | 278,392,603,102,167,820,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-25050 | netCDF in GDAL 2.4.2 through 3.0.4 has a stack-based buffer overflow in nc4_get_att (called from nc4_get_att_tc and nc_get_att_text) and in uffd_cleanup (called from netCDFDataset::~netCDFDataset and netCDFDataset::~netCDFDataset). | https://nvd.nist.gov/vuln/detail/CVE-2019-25050 |
387,524 | gdal | 767e3a56144f676ca738ef8f700e0e56035bd05a | https://github.com/OSGeo/gdal | https://github.com/OSGeo/gdal/commit/767e3a56144f676ca738ef8f700e0e56035bd05a | netCDF: avoid buffer overflow. master only. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15143. Credit to OSS Fuzz | 0 | std::string& attrf(int ncid, int varId, const char * attrName, std::string& alloc)
{
size_t len = 0;
nc_inq_attlen(ncid, varId, attrName, &len);
if(len < 1)
{
alloc.clear();
return alloc;
}
alloc.resize(len);
memset(&alloc[0], 0, ... | 306,160,861,738,433,630,000,000,000,000,000,000,000 | netcdfsg.cpp | 79,552,374,247,323,930,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-25050 | netCDF in GDAL 2.4.2 through 3.0.4 has a stack-based buffer overflow in nc4_get_att (called from nc4_get_att_tc and nc_get_att_text) and in uffd_cleanup (called from netCDFDataset::~netCDFDataset and netCDFDataset::~netCDFDataset). | https://nvd.nist.gov/vuln/detail/CVE-2019-25050 |
206,840 | linux | 5d78e1c2b7f4be00bbe62141603a631dc7812f35 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d78e1c2b7f4be00bbe62141603a631dc7812f35 | ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
syzbot found the following crash on:
general protection fault: 0000 [#1] SMP KASAN
RIP: 0010:snd_usb_pipe_sanity_check+0x80/0x130 sound/usb/helper.c:75
Call Trace:
snd_usb_motu_microbookii_communicate.constprop.0+0xa0/0x2fb sound/usb/quirks.c:1007
s... | 1 | int snd_usb_pipe_sanity_check(struct usb_device *dev, unsigned int pipe)
{
static const int pipetypes[4] = {
PIPE_CONTROL, PIPE_ISOCHRONOUS, PIPE_BULK, PIPE_INTERRUPT
};
struct usb_host_endpoint *ep;
ep = usb_pipe_endpoint(dev, pipe);
if (usb_pipetype(pipe) != pipetypes[usb_endpoint_type(&ep->desc)])
return -... | 333,287,191,300,317,920,000,000,000,000,000,000,000 | helper.c | 22,104,621,637,227,308,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-15222 | An issue was discovered in the Linux kernel before 5.2.8. There is a NULL pointer dereference caused by a malicious USB device in the sound/usb/helper.c (motu_microbookii) driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15222 |
387,530 | linux | 5d78e1c2b7f4be00bbe62141603a631dc7812f35 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d78e1c2b7f4be00bbe62141603a631dc7812f35 | ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
syzbot found the following crash on:
general protection fault: 0000 [#1] SMP KASAN
RIP: 0010:snd_usb_pipe_sanity_check+0x80/0x130 sound/usb/helper.c:75
Call Trace:
snd_usb_motu_microbookii_communicate.constprop.0+0xa0/0x2fb sound/usb/quirks.c:1007
s... | 0 | int snd_usb_pipe_sanity_check(struct usb_device *dev, unsigned int pipe)
{
static const int pipetypes[4] = {
PIPE_CONTROL, PIPE_ISOCHRONOUS, PIPE_BULK, PIPE_INTERRUPT
};
struct usb_host_endpoint *ep;
ep = usb_pipe_endpoint(dev, pipe);
if (!ep || usb_pipetype(pipe) != pipetypes[usb_endpoint_type(&ep->desc)])
r... | 74,773,652,563,888,680,000,000,000,000,000,000,000 | helper.c | 326,912,006,013,356,820,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-15222 | An issue was discovered in the Linux kernel before 5.2.8. There is a NULL pointer dereference caused by a malicious USB device in the sound/usb/helper.c (motu_microbookii) driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15222 |
206,841 | linux | 31e0456de5be379b10fea0fa94a681057114a96e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=31e0456de5be379b10fea0fa94a681057114a96e | media: usb: siano: Fix general protection fault in smsusb
The syzkaller USB fuzzer found a general-protection-fault bug in the
smsusb part of the Siano DVB driver. The fault occurs during probe
because the driver assumes without checking that the device has both
IN and OUT endpoints and the IN endpoint is ep1.
By sl... | 1 | static int smsusb_init_device(struct usb_interface *intf, int board_id)
{
struct smsdevice_params_t params;
struct smsusb_device_t *dev;
void *mdev;
int i, rc;
/* create device object */
dev = kzalloc(sizeof(struct smsusb_device_t), GFP_KERNEL);
if (!dev)
return -ENOMEM;
memset(¶ms, 0, sizeof(params));
... | 306,883,539,595,921,800,000,000,000,000,000,000,000 | smsusb.c | 262,316,471,016,355,950,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-15218 | An issue was discovered in the Linux kernel before 5.1.8. There is a NULL pointer dereference caused by a malicious USB device in the drivers/media/usb/siano/smsusb.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15218 |
387,536 | linux | 31e0456de5be379b10fea0fa94a681057114a96e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=31e0456de5be379b10fea0fa94a681057114a96e | media: usb: siano: Fix general protection fault in smsusb
The syzkaller USB fuzzer found a general-protection-fault bug in the
smsusb part of the Siano DVB driver. The fault occurs during probe
because the driver assumes without checking that the device has both
IN and OUT endpoints and the IN endpoint is ep1.
By sl... | 0 | static int smsusb_init_device(struct usb_interface *intf, int board_id)
{
struct smsdevice_params_t params;
struct smsusb_device_t *dev;
void *mdev;
int i, rc;
int in_maxp;
/* create device object */
dev = kzalloc(sizeof(struct smsusb_device_t), GFP_KERNEL);
if (!dev)
return -ENOMEM;
memset(¶ms, 0, siz... | 199,166,937,864,345,860,000,000,000,000,000,000,000 | smsusb.c | 151,820,172,043,420,060,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-15218 | An issue was discovered in the Linux kernel before 5.1.8. There is a NULL pointer dereference caused by a malicious USB device in the drivers/media/usb/siano/smsusb.c driver. | https://nvd.nist.gov/vuln/detail/CVE-2019-15218 |
206,890 | kvm | 5678de3f15010b9022ee45673f33bcfc71d47b60 | http://git.kernel.org/?p=linux/kernel/git/avi/kvm | https://git.kernel.org/cgit/virt/kvm/kvm.git/commit/?id=5678de3f15010b9022ee45673f33bcfc71d47b60 | KVM: ioapic: fix assignment of ioapic->rtc_status.pending_eoi (CVE-2014-0155)
QE reported that they got the BUG_ON in ioapic_service to trigger.
I cannot reproduce it, but there are two reasons why this could happen.
The less likely but also easiest one, is when kvm_irq_delivery_to_apic
does not deliver to any APIC a... | 1 | static int ioapic_service(struct kvm_ioapic *ioapic, int irq, bool line_status)
{
union kvm_ioapic_redirect_entry *entry = &ioapic->redirtbl[irq];
struct kvm_lapic_irq irqe;
int ret;
if (entry->fields.mask)
return -1;
ioapic_debug("dest=%x dest_mode=%x delivery_mode=%x "
"vector=%x trig_mode=%x\n",
... | 190,891,708,320,983,970,000,000,000,000,000,000,000 | ioapic.c | 232,787,089,094,728,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0155 | The ioapic_deliver function in virt/kvm/ioapic.c in the Linux kernel through 3.14.1 does not properly validate the kvm_irq_delivery_to_apic return value, which allows guest OS users to cause a denial of service (host OS crash) via a crafted entry in the redirection table of an I/O APIC. NOTE: the affected code was mov... | https://nvd.nist.gov/vuln/detail/CVE-2014-0155 |
388,393 | kvm | 5678de3f15010b9022ee45673f33bcfc71d47b60 | http://git.kernel.org/?p=linux/kernel/git/avi/kvm | https://git.kernel.org/cgit/virt/kvm/kvm.git/commit/?id=5678de3f15010b9022ee45673f33bcfc71d47b60 | KVM: ioapic: fix assignment of ioapic->rtc_status.pending_eoi (CVE-2014-0155)
QE reported that they got the BUG_ON in ioapic_service to trigger.
I cannot reproduce it, but there are two reasons why this could happen.
The less likely but also easiest one, is when kvm_irq_delivery_to_apic
does not deliver to any APIC a... | 0 | static int ioapic_service(struct kvm_ioapic *ioapic, int irq, bool line_status)
{
union kvm_ioapic_redirect_entry *entry = &ioapic->redirtbl[irq];
struct kvm_lapic_irq irqe;
int ret;
if (entry->fields.mask)
return -1;
ioapic_debug("dest=%x dest_mode=%x delivery_mode=%x "
"vector=%x trig_mode=%x\n",
... | 13,761,285,061,459,642,000,000,000,000,000,000,000 | ioapic.c | 50,533,362,644,565,990,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-0155 | The ioapic_deliver function in virt/kvm/ioapic.c in the Linux kernel through 3.14.1 does not properly validate the kvm_irq_delivery_to_apic return value, which allows guest OS users to cause a denial of service (host OS crash) via a crafted entry in the redirection table of an I/O APIC. NOTE: the affected code was mov... | https://nvd.nist.gov/vuln/detail/CVE-2014-0155 |
206,891 | exiv2 | ae49250942f4395639961abeed3c15920fcd7241 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/ae49250942f4395639961abeed3c15920fcd7241 | Check in Image::printIFDStructure if seek and reads are OK | 1 | void Image::printIFDStructure(BasicIo& io, std::ostream& out, Exiv2::PrintStructureOption option,uint32_t start,bool bSwap,char c,int depth)
{
depth++;
bool bFirst = true ;
// buffer
const size_t dirSize = 32;
DataBuf dir(dirSize);
bool bPrint = option == kpsB... | 202,875,531,202,305,500,000,000,000,000,000,000,000 | image.cpp | 145,449,177,502,050,600,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-18915 | There is an infinite loop in the Exiv2::Image::printIFDStructure function of image.cpp in Exiv2 0.27-RC1. A crafted input will lead to a remote denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2018-18915 |
388,426 | exiv2 | ae49250942f4395639961abeed3c15920fcd7241 | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/ae49250942f4395639961abeed3c15920fcd7241 | Check in Image::printIFDStructure if seek and reads are OK | 0 | void Image::printIFDStructure(BasicIo& io, std::ostream& out, Exiv2::PrintStructureOption option,uint32_t start,bool bSwap,char c,int depth)
{
depth++;
bool bFirst = true ;
// buffer
const size_t dirSize = 32;
DataBuf dir(dirSize);
bool bPrint = option == kpsB... | 278,997,229,994,351,620,000,000,000,000,000,000,000 | image.cpp | 231,127,827,725,196,200,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2018-18915 | There is an infinite loop in the Exiv2::Image::printIFDStructure function of image.cpp in Exiv2 0.27-RC1. A crafted input will lead to a remote denial of service attack. | https://nvd.nist.gov/vuln/detail/CVE-2018-18915 |
206,903 | ruby | 47165eed264d357e78e27371cfef20d5c2bde5d9 | https://github.com/ruby/ruby | https://github.com/ruby/ruby/commit/47165eed264d357e78e27371cfef20d5c2bde5d9 | merge revision(s) 62991,63000:
unixsocket.c: check NUL bytes
* ext/socket/unixsocket.c (rsock_init_unixsock): check NUL bytes.
https://hackerone.com/reports/302997
unixsocket.c: abstract namespace
* ext/socket/unixsocket.c (unixsock_path_value): fix r62991 for
Linux abstract namespace.
git-svn-id: svn+ss... | 1 | rsock_init_unixsock(VALUE sock, VALUE path, int server)
{
struct sockaddr_un sockaddr;
socklen_t sockaddrlen;
int fd, status;
rb_io_t *fptr;
SafeStringValue(path);
INIT_SOCKADDR_UN(&sockaddr, sizeof(struct sockaddr_un));
if (sizeof(sockaddr.sun_path) < (size_t)RSTRING_LEN(path)) {
... | 85,233,085,923,842,290,000,000,000,000,000,000,000 | unixsocket.c | 171,821,696,119,910,770,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-8779 | In Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1, the UNIXServer.open and UNIXSocket.open methods are not checked for null characters. It may be connected to an unintended socket. | https://nvd.nist.gov/vuln/detail/CVE-2018-8779 |
388,746 | ruby | 47165eed264d357e78e27371cfef20d5c2bde5d9 | https://github.com/ruby/ruby | https://github.com/ruby/ruby/commit/47165eed264d357e78e27371cfef20d5c2bde5d9 | merge revision(s) 62991,63000:
unixsocket.c: check NUL bytes
* ext/socket/unixsocket.c (rsock_init_unixsock): check NUL bytes.
https://hackerone.com/reports/302997
unixsocket.c: abstract namespace
* ext/socket/unixsocket.c (unixsock_path_value): fix r62991 for
Linux abstract namespace.
git-svn-id: svn+ss... | 0 | rsock_init_unixsock(VALUE sock, VALUE path, int server)
{
struct sockaddr_un sockaddr;
socklen_t sockaddrlen;
int fd, status;
rb_io_t *fptr;
path = unixsock_path_value(path);
INIT_SOCKADDR_UN(&sockaddr, sizeof(struct sockaddr_un));
if (sizeof(sockaddr.sun_path) < (size_t)RSTRING_LEN(path))... | 261,216,877,327,790,200,000,000,000,000,000,000,000 | unixsocket.c | 330,131,633,185,445,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-8779 | In Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1, the UNIXServer.open and UNIXSocket.open methods are not checked for null characters. It may be connected to an unintended socket. | https://nvd.nist.gov/vuln/detail/CVE-2018-8779 |
206,905 | libssh2 | ca5222ea819cc5ed797860070b4c6c1aeeb28420 | https://github.com/libssh2/libssh2 | https://github.com/libssh2/libssh2/commit/ca5222ea819cc5ed797860070b4c6c1aeeb28420 | diffie_hellman_sha256: convert bytes to bits
As otherwise we get far too small numbers.
Reported-by: Andreas Schneider
CVE-2016-0787 | 1 | static int diffie_hellman_sha256(LIBSSH2_SESSION *session,
_libssh2_bn *g,
_libssh2_bn *p,
int group_order,
unsigned char packet_type_init,
unsigned char p... | 314,928,970,019,110,650,000,000,000,000,000,000,000 | kex.c | 113,720,277,031,582,980,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-0787 | The diffie_hellman_sha256 function in kex.c in libssh2 before 1.7.0 improperly truncates secrets to 128 or 256 bits, which makes it easier for man-in-the-middle attackers to decrypt or intercept SSH sessions via unspecified vectors, aka a "bits/bytes confusion bug." | https://nvd.nist.gov/vuln/detail/CVE-2016-0787 |
388,799 | libssh2 | ca5222ea819cc5ed797860070b4c6c1aeeb28420 | https://github.com/libssh2/libssh2 | https://github.com/libssh2/libssh2/commit/ca5222ea819cc5ed797860070b4c6c1aeeb28420 | diffie_hellman_sha256: convert bytes to bits
As otherwise we get far too small numbers.
Reported-by: Andreas Schneider
CVE-2016-0787 | 0 | static int diffie_hellman_sha1(LIBSSH2_SESSION *session,
_libssh2_bn *g,
_libssh2_bn *p,
int group_order,
unsigned char packet_type_init,
unsigned char packet_type_r... | 71,553,697,357,270,620,000,000,000,000,000,000,000 | kex.c | 298,133,920,254,720,200,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-0787 | The diffie_hellman_sha256 function in kex.c in libssh2 before 1.7.0 improperly truncates secrets to 128 or 256 bits, which makes it easier for man-in-the-middle attackers to decrypt or intercept SSH sessions via unspecified vectors, aka a "bits/bytes confusion bug." | https://nvd.nist.gov/vuln/detail/CVE-2016-0787 |
206,906 | mujs | 25821e6d74fab5fcc200fe5e818362e03e114428 | https://github.com/ccxvii/mujs | http://git.ghostscript.com/?p=mujs.git;a=commit;h=25821e6d74fab5fcc200fe5e818362e03e114428 | Fix 698920: Guard jsdtoa from integer overflow wreaking havoc. | 1 | js_strtod(const char *string, char **endPtr)
{
int sign, expSign = FALSE;
double fraction, dblExp, *d;
register const char *p;
register int c;
/* Exponent read from "EX" field. */
int exp = 0;
/* Exponent that derives from the fractional part. Under normal
* circumstances, it is the negative of the number of... | 108,169,533,684,780,730,000,000,000,000,000,000,000 | jsdtoa.c | 202,875,402,184,535,700,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-6191 | The js_strtod function in jsdtoa.c in Artifex MuJS through 1.0.2 has an integer overflow because of incorrect exponent validation. | https://nvd.nist.gov/vuln/detail/CVE-2018-6191 |
388,829 | mujs | 25821e6d74fab5fcc200fe5e818362e03e114428 | https://github.com/ccxvii/mujs | http://git.ghostscript.com/?p=mujs.git;a=commit;h=25821e6d74fab5fcc200fe5e818362e03e114428 | Fix 698920: Guard jsdtoa from integer overflow wreaking havoc. | 0 | js_strtod(const char *string, char **endPtr)
{
int sign, expSign = FALSE;
double fraction, dblExp, *d;
register const char *p;
register int c;
/* Exponent read from "EX" field. */
int exp = 0;
/* Exponent that derives from the fractional part. Under normal
* circumstances, it is the negative of the number of... | 44,115,557,044,198,260,000,000,000,000,000,000,000 | jsdtoa.c | 85,371,735,835,100,680,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-6191 | The js_strtod function in jsdtoa.c in Artifex MuJS through 1.0.2 has an integer overflow because of incorrect exponent validation. | https://nvd.nist.gov/vuln/detail/CVE-2018-6191 |
206,907 | ImageMagick | 361ed689cc8e56fd125f9d0d6508e9eb303bdca6 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/361ed689cc8e56fd125f9d0d6508e9eb303bdca6 | https://github.com/ImageMagick/ImageMagick/issues/1009 | 1 | static MagickBooleanType IsWEBPImageLossless(const unsigned char *stream,
const size_t length)
{
#define VP8_CHUNK_INDEX 15
#define LOSSLESS_FLAG 'L'
#define EXTENDED_HEADER 'X'
#define VP8_CHUNK_HEADER "VP8"
#define VP8_CHUNK_HEADER_SIZE 3
#define RIFF_HEADER_SIZE 12
#define VP8X_CHUNK_SIZE 10
#define TAG_SIZ... | 215,939,365,067,930,740,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2018-9135 | In ImageMagick 7.0.7-24 Q16, there is a heap-based buffer over-read in IsWEBPImageLossless in coders/webp.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-9135 |
388,834 | ImageMagick | 361ed689cc8e56fd125f9d0d6508e9eb303bdca6 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/361ed689cc8e56fd125f9d0d6508e9eb303bdca6 | https://github.com/ImageMagick/ImageMagick/issues/1009 | 0 | static MagickBooleanType IsWEBPImageLossless(const unsigned char *stream,
const size_t length)
{
#define VP8_CHUNK_INDEX 15
#define LOSSLESS_FLAG 'L'
#define EXTENDED_HEADER 'X'
#define VP8_CHUNK_HEADER "VP8"
#define VP8_CHUNK_HEADER_SIZE 3
#define RIFF_HEADER_SIZE 12
#define VP8X_CHUNK_SIZE 10
#define TAG_SIZ... | 310,424,004,346,590,700,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2018-9135 | In ImageMagick 7.0.7-24 Q16, there is a heap-based buffer over-read in IsWEBPImageLossless in coders/webp.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-9135 |
206,908 | radvd | 7dc53cc3b792775369bf0b2f053a3f4ed5d87e3d | https://github.com/reubenhwk/radvd | https://github.com/reubenhwk/radvd/commit/7dc53cc3b792775369bf0b2f053a3f4ed5d87e3d | Really exit on privsep init failure. | 1 | main(int argc, char *argv[])
{
char pidstr[16];
ssize_t ret;
int c, log_method;
char *logfile, *pidfile;
int facility, fd;
char *username = NULL;
char *chrootdir = NULL;
int configtest = 0;
int singleprocess = 0;
#ifdef HAVE_GETOPT_LONG
int opt_idx;
#endif
pname = ((pname=strrchr(argv[0],'/')) != NULL)?pnam... | 226,845,491,059,499,040,000,000,000,000,000,000,000 | radvd.c | 268,439,042,886,540,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3603 | The router advertisement daemon (radvd) before 1.8.2 does not properly handle errors in the privsep_init function, which causes the radvd daemon to run as root and has an unspecified impact. | https://nvd.nist.gov/vuln/detail/CVE-2011-3603 |
388,849 | radvd | 7dc53cc3b792775369bf0b2f053a3f4ed5d87e3d | https://github.com/reubenhwk/radvd | https://github.com/reubenhwk/radvd/commit/7dc53cc3b792775369bf0b2f053a3f4ed5d87e3d | Really exit on privsep init failure. | 0 | main(int argc, char *argv[])
{
char pidstr[16];
ssize_t ret;
int c, log_method;
char *logfile, *pidfile;
int facility, fd;
char *username = NULL;
char *chrootdir = NULL;
int configtest = 0;
int singleprocess = 0;
#ifdef HAVE_GETOPT_LONG
int opt_idx;
#endif
pname = ((pname=strrchr(argv[0],'/')) != NULL)?pnam... | 139,671,564,459,141,500,000,000,000,000,000,000,000 | radvd.c | 135,446,911,792,039,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3603 | The router advertisement daemon (radvd) before 1.8.2 does not properly handle errors in the privsep_init function, which causes the radvd daemon to run as root and has an unspecified impact. | https://nvd.nist.gov/vuln/detail/CVE-2011-3603 |
206,915 | exim | cf3cd306062a08969c41a1cdd32c6855f1abecf1 | https://github.com/Exim/exim | https://github.com/Exim/exim/commit/cf3cd306062a08969c41a1cdd32c6855f1abecf1 | Fix base64d() buffer size (CVE-2018-6789)
Credits for discovering this bug: Meh Chang <meh@devco.re>
(cherry picked from commit 062990cc1b2f9e5d82a413b53c8f0569075de700) | 1 | b64decode(const uschar *code, uschar **ptr)
{
int x, y;
uschar *result = store_get(3*(Ustrlen(code)/4) + 1);
*ptr = result;
/* Each cycle of the loop handles a quantum of 4 input bytes. For the last
quantum this may decode to 1, 2, or 3 output bytes. */
while ((x = *code++) != 0)
{
if (isspace(x)) continue;
/*... | 169,533,421,853,080,130,000,000,000,000,000,000,000 | base64.c | 186,136,829,121,471,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-6789 | An issue was discovered in the base64d function in the SMTP listener in Exim before 4.90.1. By sending a handcrafted message, a buffer overflow may happen. This can be used to execute code remotely. | https://nvd.nist.gov/vuln/detail/CVE-2018-6789 |
388,930 | exim | cf3cd306062a08969c41a1cdd32c6855f1abecf1 | https://github.com/Exim/exim | https://github.com/Exim/exim/commit/cf3cd306062a08969c41a1cdd32c6855f1abecf1 | Fix base64d() buffer size (CVE-2018-6789)
Credits for discovering this bug: Meh Chang <meh@devco.re>
(cherry picked from commit 062990cc1b2f9e5d82a413b53c8f0569075de700) | 0 | b64decode(const uschar *code, uschar **ptr)
{
int x, y;
uschar *result;
{
int l = Ustrlen(code);
*ptr = result = store_get(1 + l/4 * 3 + l%4);
}
/* Each cycle of the loop handles a quantum of 4 input bytes. For the last
quantum this may decode to 1, 2, or 3 output bytes. */
while ((x = *code++) != 0)
{
if (... | 197,855,288,838,163,700,000,000,000,000,000,000,000 | base64.c | 283,963,400,902,695,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2018-6789 | An issue was discovered in the base64d function in the SMTP listener in Exim before 4.90.1. By sending a handcrafted message, a buffer overflow may happen. This can be used to execute code remotely. | https://nvd.nist.gov/vuln/detail/CVE-2018-6789 |
206,916 | tip | 7bdb157cdebbf95a1cd94ed2e01b338714075d00 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=7bdb157cdebbf95a1cd94ed2e01b338714075d00 | perf/core: Fix a memory leak in perf_event_parse_addr_filter()
As shown through runtime testing, the "filename" allocation is not
always freed in perf_event_parse_addr_filter().
There are three possible ways that this could happen:
- It could be allocated twice on subsequent iterations through the loop,
- or leake... | 1 | perf_event_parse_addr_filter(struct perf_event *event, char *fstr,
struct list_head *filters)
{
struct perf_addr_filter *filter = NULL;
char *start, *orig, *filename = NULL;
substring_t args[MAX_OPT_ARGS];
int state = IF_STATE_ACTION, token;
unsigned int kernel = 0;
int ret = -EINVAL;
orig = fstr = kstr... | 67,280,376,106,311,590,000,000,000,000,000,000,000 | core.c | 222,904,444,309,688,040,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-25704 | A flaw memory leak in the Linux kernel performance monitoring subsystem was found in the way if using PERF_EVENT_IOC_SET_FILTER. A local user could use this flaw to starve the resources causing denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-25704 |
389,172 | tip | 7bdb157cdebbf95a1cd94ed2e01b338714075d00 | http://git.kernel.org/cgit/linux/kernel/git/tip/tip | https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=7bdb157cdebbf95a1cd94ed2e01b338714075d00 | perf/core: Fix a memory leak in perf_event_parse_addr_filter()
As shown through runtime testing, the "filename" allocation is not
always freed in perf_event_parse_addr_filter().
There are three possible ways that this could happen:
- It could be allocated twice on subsequent iterations through the loop,
- or leake... | 0 | perf_event_parse_addr_filter(struct perf_event *event, char *fstr,
struct list_head *filters)
{
struct perf_addr_filter *filter = NULL;
char *start, *orig, *filename = NULL;
substring_t args[MAX_OPT_ARGS];
int state = IF_STATE_ACTION, token;
unsigned int kernel = 0;
int ret = -EINVAL;
orig = fstr = kstr... | 313,872,987,792,086,280,000,000,000,000,000,000,000 | core.c | 258,496,977,675,044,950,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2020-25704 | A flaw memory leak in the Linux kernel performance monitoring subsystem was found in the way if using PERF_EVENT_IOC_SET_FILTER. A local user could use this flaw to starve the resources causing denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-25704 |
206,920 | Pillow | 4e0d9b0b9740d258ade40cce248c93777362ac1e | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/4e0d9b0b9740d258ade40cce248c93777362ac1e | fix integer overflow in Resample.c | 1 | ImagingResampleHorizontal(Imaging imIn, int xsize, int filter)
{
ImagingSectionCookie cookie;
Imaging imOut;
struct filter *filterp;
float support, scale, filterscale;
float center, ww, ss, ss0, ss1, ss2, ss3;
int xx, yy, x, kmax, xmin, xmax;
int *xbounds;
float *k, *kk;
/* check fi... | 247,316,705,893,206,600,000,000,000,000,000,000,000 | Resample.c | 20,378,241,410,752,090,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-4009 | Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-4009 |
389,232 | Pillow | 4e0d9b0b9740d258ade40cce248c93777362ac1e | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/4e0d9b0b9740d258ade40cce248c93777362ac1e | fix integer overflow in Resample.c | 0 | ImagingResampleHorizontal(Imaging imIn, int xsize, int filter)
{
ImagingSectionCookie cookie;
Imaging imOut;
struct filter *filterp;
float support, scale, filterscale;
float center, ww, ss, ss0, ss1, ss2, ss3;
int xx, yy, x, kmax, xmin, xmax;
int *xbounds;
float *k, *kk;
/* check fi... | 177,873,929,825,345,060,000,000,000,000,000,000,000 | Resample.c | 250,161,017,870,259,300,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2016-4009 | Integer overflow in the ImagingResampleHorizontal function in libImaging/Resample.c in Pillow before 3.1.1 allows remote attackers to have unspecified impact via negative values of the new size, which triggers a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2016-4009 |
206,937 | qemu | 79fa99831debc9782087e834382c577215f2f511 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/79fa99831debc9782087e834382c577215f2f511 | hw/audio/intel-hda: Restrict DMA engine to memories (not MMIO devices)
Issue #542 reports a reentrancy problem when the DMA engine accesses
the HDA controller I/O registers. Fix by restricting the DMA engine
to memories regions (forbidding MMIO devices such the HDA controller).
Reported-by: OSS-Fuzz (Issue 28435)
Rep... | 1 | static void intel_hda_response(HDACodecDevice *dev, bool solicited, uint32_t response)
{
const MemTxAttrs attrs = MEMTXATTRS_UNSPECIFIED;
HDACodecBus *bus = HDA_BUS(dev->qdev.parent_bus);
IntelHDAState *d = container_of(bus, IntelHDAState, codecs);
hwaddr addr;
uint32_t wp, ex;
MemTxResult res =... | 41,906,988,843,805,190,000,000,000,000,000,000,000 | intel-hda.c | 274,788,114,901,817,540,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3611 | A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability. This flaw affects QEMU versions prior ... | https://nvd.nist.gov/vuln/detail/CVE-2021-3611 |
389,405 | qemu | 79fa99831debc9782087e834382c577215f2f511 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/79fa99831debc9782087e834382c577215f2f511 | hw/audio/intel-hda: Restrict DMA engine to memories (not MMIO devices)
Issue #542 reports a reentrancy problem when the DMA engine accesses
the HDA controller I/O registers. Fix by restricting the DMA engine
to memories regions (forbidding MMIO devices such the HDA controller).
Reported-by: OSS-Fuzz (Issue 28435)
Rep... | 0 | static void intel_hda_response(HDACodecDevice *dev, bool solicited, uint32_t response)
{
const MemTxAttrs attrs = { .memory = true };
HDACodecBus *bus = HDA_BUS(dev->qdev.parent_bus);
IntelHDAState *d = container_of(bus, IntelHDAState, codecs);
hwaddr addr;
uint32_t wp, ex;
MemTxResult res = MEM... | 213,234,049,856,760,240,000,000,000,000,000,000,000 | intel-hda.c | 53,583,568,370,726,130,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3611 | A stack overflow vulnerability was found in the Intel HD Audio device (intel-hda) of QEMU. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. The highest threat from this vulnerability is to system availability. This flaw affects QEMU versions prior ... | https://nvd.nist.gov/vuln/detail/CVE-2021-3611 |
206,939 | liblouis | b5049cb17ae3d15b2b26890de0e24d0fecc080f5 | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/b5049cb17ae3d15b2b26890de0e24d0fecc080f5 | Fix yet another buffer overflow in the braille table parser
Reported by Henri Salo
Fixes #593 | 1 | compileHyphenation(FileInfo *nested, CharsString *encoding, int *lastToken,
TranslationTableHeader **table) {
CharsString hyph;
HyphenationTrans *holdPointer;
HyphenHashTab *hashTab;
CharsString word;
char pattern[MAXSTRING];
unsigned int stateNum = 0, lastState = 0;
int i, j, k = encoding->length;
widechar c... | 190,784,215,388,328,050,000,000,000,000,000,000,000 | compileTranslationTable.c | 247,192,396,646,028,800,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-11685 | Liblouis 3.5.0 has a stack-based Buffer Overflow in the function compileHyphenation in compileTranslationTable.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-11685 |
389,468 | liblouis | b5049cb17ae3d15b2b26890de0e24d0fecc080f5 | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/b5049cb17ae3d15b2b26890de0e24d0fecc080f5 | Fix yet another buffer overflow in the braille table parser
Reported by Henri Salo
Fixes #593 | 0 | compileHyphenation(FileInfo *nested, CharsString *encoding, int *lastToken,
TranslationTableHeader **table) {
CharsString hyph;
HyphenationTrans *holdPointer;
HyphenHashTab *hashTab;
CharsString word;
char pattern[MAXSTRING + 1];
unsigned int stateNum = 0, lastState = 0;
int i, j, k = encoding->length;
widech... | 33,607,864,814,064,217,000,000,000,000,000,000,000 | compileTranslationTable.c | 143,489,673,509,276,910,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-11685 | Liblouis 3.5.0 has a stack-based Buffer Overflow in the function compileHyphenation in compileTranslationTable.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-11685 |
206,941 | sqlite | e41fd72acc7a06ce5a6a7d28154db1ffe8ba37a8 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/e41fd72acc7a06ce5a6a7d28154db1ffe8ba37a8 | Enhance the rtreenode() function of rtree (used for testing) so that it
uses the newer sqlite3_str object for better performance and improved
error reporting.
FossilOrigin-Name: 90acdbfce9c088582d5165589f7eac462b00062bbfffacdcc786eb9cf3ea5377 | 1 | static void rtreenode(sqlite3_context *ctx, int nArg, sqlite3_value **apArg){
char *zText = 0;
RtreeNode node;
Rtree tree;
int ii;
UNUSED_PARAMETER(nArg);
memset(&node, 0, sizeof(RtreeNode));
memset(&tree, 0, sizeof(Rtree));
tree.nDim = (u8)sqlite3_value_int(apArg[0]);
tree.nDim2 = tree.nDim*2;
tre... | 182,190,151,530,441,050,000,000,000,000,000,000,000 | rtree.c | 2,472,658,288,289,194,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-8457 | SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables. | https://nvd.nist.gov/vuln/detail/CVE-2019-8457 |
389,648 | sqlite | e41fd72acc7a06ce5a6a7d28154db1ffe8ba37a8 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/e41fd72acc7a06ce5a6a7d28154db1ffe8ba37a8 | Enhance the rtreenode() function of rtree (used for testing) so that it
uses the newer sqlite3_str object for better performance and improved
error reporting.
FossilOrigin-Name: 90acdbfce9c088582d5165589f7eac462b00062bbfffacdcc786eb9cf3ea5377 | 0 | static void rtreenode(sqlite3_context *ctx, int nArg, sqlite3_value **apArg){
RtreeNode node;
Rtree tree;
int ii;
int nData;
int errCode;
sqlite3_str *pOut;
UNUSED_PARAMETER(nArg);
memset(&node, 0, sizeof(RtreeNode));
memset(&tree, 0, sizeof(Rtree));
tree.nDim = (u8)sqlite3_value_int(apArg[0]);
i... | 234,443,701,030,741,180,000,000,000,000,000,000,000 | rtree.c | 106,313,071,011,226,780,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-8457 | SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree tables. | https://nvd.nist.gov/vuln/detail/CVE-2019-8457 |
206,943 | ImageMagick | 4b352c0be410ad900469a079e389178f878aded8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4b352c0be410ad900469a079e389178f878aded8 | https://github.com/ImageMagick/ImageMagick/issues/1191 | 1 | static Image *ReadMIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define BZipMaxExtent(x) ((x)+((x)/100)+600)
#define LZMAMaxExtent(x) ((x)+((x)/3)+128)
#define ThrowMIFFException(exception,message) \
{ \
if (quantum_info != (QuantumInfo *) NULL) \
quantum_info=DestroyQuantumInfo(quantum_i... | 194,682,057,306,530,230,000,000,000,000,000,000,000 | miff.c | 223,710,451,258,097,630,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2018-14436 | ImageMagick 7.0.8-4 has a memory leak in ReadMIFFImage in coders/miff.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-14436 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.