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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
446,840 | linux | 29eb31542787e1019208a2e1047bb7c76c069536 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=29eb31542787e1019208a2e1047bb7c76c069536 | yam: fix a memory leak in yam_siocdevprivate()
ym needs to be free when ym->cmd != SIOCYAMSMCS.
Fixes: 0781168e23a2 ("yam: fix a missing-check bug")
Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net> | 0 | static int yam_siocdevprivate(struct net_device *dev, struct ifreq *ifr, void __user *data, int cmd)
{
struct yam_port *yp = netdev_priv(dev);
struct yamdrv_ioctl_cfg yi;
struct yamdrv_ioctl_mcs *ym;
int ioctl_cmd;
if (copy_from_user(&ioctl_cmd, data, sizeof(int)))
return -EFAULT;
if (yp->magic != YAM_MAGIC)
... | 330,971,924,165,969,600,000,000,000,000,000,000,000 | yam.c | 326,370,070,443,985,540,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2022-24959 | An issue was discovered in the Linux kernel before 5.16.5. There is a memory leak in yam_siocdevprivate in drivers/net/hamradio/yam.c. | https://nvd.nist.gov/vuln/detail/CVE-2022-24959 |
211,157 | ImageMagick6 | 6ba5e4b1673d75988d8dde38118b495a342823c8 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/6ba5e4b1673d75988d8dde38118b495a342823c8 | [FG-VD-19-136] ImageMagick Convert SVG MacOS Denial Of Service | 1 | static Image *ReadSVGImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MaxTextExtent];
FILE
*file;
Image
*image,
*next;
int
status,
unique_file;
ssize_t
n;
SVGInfo
*svg_info;
unsigned char
message[MaxTextExtent];
xmlSAXHandler
sax_... | 174,723,574,586,132,520,000,000,000,000,000,000,000 | svg.c | 61,952,333,201,604,340,000,000,000,000,000,000,000 | [
"CWE-674"
] | CVE-2019-18853 | ImageMagick before 7.0.9-0 allows remote attackers to cause a denial of service because XML_PARSE_HUGE is not properly restricted in coders/svg.c, related to SVG and libxml2. | https://nvd.nist.gov/vuln/detail/CVE-2019-18853 |
446,854 | ImageMagick6 | 6ba5e4b1673d75988d8dde38118b495a342823c8 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/6ba5e4b1673d75988d8dde38118b495a342823c8 | [FG-VD-19-136] ImageMagick Convert SVG MacOS Denial Of Service | 0 | static Image *ReadSVGImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MaxTextExtent];
FILE
*file;
Image
*image,
*next;
int
status,
unique_file;
ssize_t
n;
SVGInfo
*svg_info;
unsigned char
message[MaxTextExtent];
xmlSAXHandler
sax_... | 288,616,536,342,779,700,000,000,000,000,000,000,000 | svg.c | 194,337,343,082,853,770,000,000,000,000,000,000,000 | [
"CWE-674"
] | CVE-2019-18853 | ImageMagick before 7.0.9-0 allows remote attackers to cause a denial of service because XML_PARSE_HUGE is not properly restricted in coders/svg.c, related to SVG and libxml2. | https://nvd.nist.gov/vuln/detail/CVE-2019-18853 |
211,180 | ImageMagick | 6ad5fc3c9b652eec27fc0b1a0817159f8547d5d9 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6ad5fc3c9b652eec27fc0b1a0817159f8547d5d9 | https://github.com/ImageMagick/ImageMagick/issues/716 | 1 | WandExport double *DrawGetStrokeDashArray(const DrawingWand *wand,
size_t *number_elements)
{
double
*dasharray;
register const double
*p;
register double
*q;
register ssize_t
i;
size_t
n;
assert(wand != (const DrawingWand *) NULL);
assert(wand->signature == MagickWandSignature)... | 190,701,875,199,553,750,000,000,000,000,000,000,000 | drawing-wand.c | 60,596,566,520,919,300,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-14505 | DrawGetStrokeDashArray in wand/drawing-wand.c in ImageMagick 7.0.7-1 mishandles certain NULL arrays, which allows attackers to perform Denial of Service (NULL pointer dereference and application crash in AcquireQuantumMemory within MagickCore/memory.c) by providing a crafted Image File as input. | https://nvd.nist.gov/vuln/detail/CVE-2017-14505 |
447,157 | ImageMagick | 6ad5fc3c9b652eec27fc0b1a0817159f8547d5d9 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6ad5fc3c9b652eec27fc0b1a0817159f8547d5d9 | https://github.com/ImageMagick/ImageMagick/issues/716 | 0 | WandExport double *DrawGetStrokeDashArray(const DrawingWand *wand,
size_t *number_elements)
{
double
*dasharray;
register const double
*p;
register double
*q;
register ssize_t
i;
size_t
n;
assert(wand != (const DrawingWand *) NULL);
assert(wand->signature == MagickWandSignature)... | 289,377,074,060,602,540,000,000,000,000,000,000,000 | drawing-wand.c | 25,004,069,858,783,370,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2017-14505 | DrawGetStrokeDashArray in wand/drawing-wand.c in ImageMagick 7.0.7-1 mishandles certain NULL arrays, which allows attackers to perform Denial of Service (NULL pointer dereference and application crash in AcquireQuantumMemory within MagickCore/memory.c) by providing a crafted Image File as input. | https://nvd.nist.gov/vuln/detail/CVE-2017-14505 |
211,182 | gnutls | 75a937d97f4fefc6f9b08e3791f151445f551cb3 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/-/commit/75a937d97f4fefc6f9b08e3791f151445f551cb3 | pre_shared_key: avoid use-after-free around realloc
Signed-off-by: Daiki Ueno <ueno@gnu.org> | 1 | client_send_params(gnutls_session_t session,
gnutls_buffer_t extdata,
const gnutls_psk_client_credentials_t cred)
{
int ret, ext_offset = 0;
uint8_t binder_value[MAX_HASH_SIZE];
size_t spos;
gnutls_datum_t username = {NULL, 0};
gnutls_datum_t user_key = {NULL, 0}, rkey = {NULL, 0};
gnutls_datum_t client... | 96,770,617,552,518,340,000,000,000,000,000,000,000 | pre_shared_key.c | 307,508,124,839,034,900,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2021-20232 | A flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences. | https://nvd.nist.gov/vuln/detail/CVE-2021-20232 |
447,242 | gnutls | 75a937d97f4fefc6f9b08e3791f151445f551cb3 | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/-/commit/75a937d97f4fefc6f9b08e3791f151445f551cb3 | pre_shared_key: avoid use-after-free around realloc
Signed-off-by: Daiki Ueno <ueno@gnu.org> | 0 | client_send_params(gnutls_session_t session,
gnutls_buffer_t extdata,
const gnutls_psk_client_credentials_t cred)
{
int ret, ext_offset = 0;
uint8_t binder_value[MAX_HASH_SIZE];
size_t spos;
gnutls_datum_t username = {NULL, 0};
gnutls_datum_t user_key = {NULL, 0}, rkey = {NULL, 0};
unsigned client_hello... | 220,006,626,874,052,200,000,000,000,000,000,000,000 | pre_shared_key.c | 214,208,699,053,971,130,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2021-20232 | A flaw was found in gnutls. A use after free issue in client_send_params in lib/ext/pre_shared_key.c may lead to memory corruption and other potential consequences. | https://nvd.nist.gov/vuln/detail/CVE-2021-20232 |
211,238 | linux | d3b0ffa1d75d5305ebe34735598993afbb8a869d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d3b0ffa1d75d5305ebe34735598993afbb8a869d | spi: gpio: prevent memory leak in spi_gpio_probe
In spi_gpio_probe an SPI master is allocated via spi_alloc_master, but
this controller should be released if devm_add_action_or_reset fails,
otherwise memory leaks. In order to avoid leak spi_contriller_put must
be called in case of failure for devm_add_action_or_reset.... | 1 | static int spi_gpio_probe(struct platform_device *pdev)
{
int status;
struct spi_master *master;
struct spi_gpio *spi_gpio;
struct device *dev = &pdev->dev;
struct spi_bitbang *bb;
const struct of_device_id *of_id;
of_id = of_match_device(spi_gpio_dt_ids, &pdev->dev);
master = spi_alloc_master(dev, s... | 270,411,884,355,529,400,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-19070 | A memory leak in the spi_gpio_probe() function in drivers/spi/spi-gpio.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering devm_add_action_or_reset() failures, aka CID-d3b0ffa1d75d. NOTE: third parties dispute the relevance of this because the system mus... | https://nvd.nist.gov/vuln/detail/CVE-2019-19070 |
447,650 | linux | d3b0ffa1d75d5305ebe34735598993afbb8a869d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d3b0ffa1d75d5305ebe34735598993afbb8a869d | spi: gpio: prevent memory leak in spi_gpio_probe
In spi_gpio_probe an SPI master is allocated via spi_alloc_master, but
this controller should be released if devm_add_action_or_reset fails,
otherwise memory leaks. In order to avoid leak spi_contriller_put must
be called in case of failure for devm_add_action_or_reset.... | 0 | static int spi_gpio_probe(struct platform_device *pdev)
{
int status;
struct spi_master *master;
struct spi_gpio *spi_gpio;
struct device *dev = &pdev->dev;
struct spi_bitbang *bb;
const struct of_device_id *of_id;
of_id = of_match_device(spi_gpio_dt_ids, &pdev->dev);
master = spi_alloc_master(dev, s... | 212,946,666,310,871,620,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-19070 | A memory leak in the spi_gpio_probe() function in drivers/spi/spi-gpio.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering devm_add_action_or_reset() failures, aka CID-d3b0ffa1d75d. NOTE: third parties dispute the relevance of this because the system mus... | https://nvd.nist.gov/vuln/detail/CVE-2019-19070 |
211,239 | ImageMagick | 30ccf9a0da1f47161b5935a95be854fe84e6c2a2 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/30ccf9a0da1f47161b5935a95be854fe84e6c2a2 | squash heap-buffer-overflow, PoC TIFF from Hardik | 1 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowTIFFException(severity,message) \
{ \
if (pixel_info != (MemoryInfo *) NULL) \
pixel_info=RelinquishVirtualMemory(pixel_info); \
if (quantum_info != (QuantumInfo *) NULL) \
quantum_info=DestroyQuantumInfo(qua... | 58,743,864,864,925,890,000,000,000,000,000,000,000 | tiff.c | 336,303,072,409,709,400,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-3213 | A heap buffer overflow issue was found in ImageMagick. When an application processes a malformed TIFF file, it could lead to undefined behavior or a crash causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2022-3213 |
447,662 | ImageMagick | 30ccf9a0da1f47161b5935a95be854fe84e6c2a2 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/30ccf9a0da1f47161b5935a95be854fe84e6c2a2 | squash heap-buffer-overflow, PoC TIFF from Hardik | 0 | static Image *ReadTIFFImage(const ImageInfo *image_info,
ExceptionInfo *exception)
{
#define ThrowTIFFException(severity,message) \
{ \
if (pixel_info != (MemoryInfo *) NULL) \
pixel_info=RelinquishVirtualMemory(pixel_info); \
if (quantum_info != (QuantumInfo *) NULL) \
quantum_info=DestroyQuantumInfo(qua... | 208,531,934,641,887,400,000,000,000,000,000,000,000 | tiff.c | 118,308,884,182,153,570,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2022-3213 | A heap buffer overflow issue was found in ImageMagick. When an application processes a malformed TIFF file, it could lead to undefined behavior or a crash causing a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2022-3213 |
211,254 | linux | 9bbfceea12a8f145097a27d7c7267af25893c060 | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9bbfceea12a8f145097a27d7c7267af25893c060 | usb: dwc3: pci: prevent memory leak in dwc3_pci_probe
In dwc3_pci_probe a call to platform_device_alloc allocates a device
which is correctly put in case of error except one case: when the call to
platform_device_add_properties fails it directly returns instead of
going to error handling. This commit replaces return w... | 1 | static int dwc3_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
{
struct property_entry *p = (struct property_entry *)id->driver_data;
struct dwc3_pci *dwc;
struct resource res[2];
int ret;
struct device *dev = &pci->dev;
ret = pcim_enable_device(pci);
if (ret) {
dev_err(dev, "failed to en... | 96,586,772,081,433,150,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-18813 | A memory leak in the dwc3_pci_probe() function in drivers/usb/dwc3/dwc3-pci.c in the Linux kernel through 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering platform_device_add_properties() failures, aka CID-9bbfceea12a8. | https://nvd.nist.gov/vuln/detail/CVE-2019-18813 |
447,727 | linux | 9bbfceea12a8f145097a27d7c7267af25893c060 | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9bbfceea12a8f145097a27d7c7267af25893c060 | usb: dwc3: pci: prevent memory leak in dwc3_pci_probe
In dwc3_pci_probe a call to platform_device_alloc allocates a device
which is correctly put in case of error except one case: when the call to
platform_device_add_properties fails it directly returns instead of
going to error handling. This commit replaces return w... | 0 | static int dwc3_pci_probe(struct pci_dev *pci, const struct pci_device_id *id)
{
struct property_entry *p = (struct property_entry *)id->driver_data;
struct dwc3_pci *dwc;
struct resource res[2];
int ret;
struct device *dev = &pci->dev;
ret = pcim_enable_device(pci);
if (ret) {
dev_err(dev, "failed to en... | 17,670,638,324,356,397,000,000,000,000,000,000,000 | None | null | [
"CWE-401"
] | CVE-2019-18813 | A memory leak in the dwc3_pci_probe() function in drivers/usb/dwc3/dwc3-pci.c in the Linux kernel through 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering platform_device_add_properties() failures, aka CID-9bbfceea12a8. | https://nvd.nist.gov/vuln/detail/CVE-2019-18813 |
211,443 | linux | 6a024330650e24556b8a18cc654ad00cfecf6c6c | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a024330650e24556b8a18cc654ad00cfecf6c6c | drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
The "param.count" value is a u64 thatcomes from the user. The code
later in the function assumes that param.count is at least one and if
it's not then it leads to an Oops when we dereference the ZERO_SIZE_PTR.
Also the addition can have an integer over... | 1 | static long ioctl_memcpy(struct fsl_hv_ioctl_memcpy __user *p)
{
struct fsl_hv_ioctl_memcpy param;
struct page **pages = NULL;
void *sg_list_unaligned = NULL;
struct fh_sg_list *sg_list = NULL;
unsigned int num_pages;
unsigned long lb_offset; /* Offset within a page of the local buffer */
unsigned int i;
lon... | 194,425,937,341,888,950,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2019-10142 | A flaw was found in the Linux kernel's freescale hypervisor manager implementation, kernel versions 5.0.x up to, excluding 5.0.17. A parameter passed to an ioctl was incorrectly validated and used in size calculations for the page size calculation. An attacker can use this flaw to crash the system, corrupt memory, or c... | https://nvd.nist.gov/vuln/detail/CVE-2019-10142 |
448,362 | linux | 6a024330650e24556b8a18cc654ad00cfecf6c6c | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a024330650e24556b8a18cc654ad00cfecf6c6c | drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
The "param.count" value is a u64 thatcomes from the user. The code
later in the function assumes that param.count is at least one and if
it's not then it leads to an Oops when we dereference the ZERO_SIZE_PTR.
Also the addition can have an integer over... | 0 | static long ioctl_memcpy(struct fsl_hv_ioctl_memcpy __user *p)
{
struct fsl_hv_ioctl_memcpy param;
struct page **pages = NULL;
void *sg_list_unaligned = NULL;
struct fh_sg_list *sg_list = NULL;
unsigned int num_pages;
unsigned long lb_offset; /* Offset within a page of the local buffer */
unsigned int i;
lon... | 129,789,420,393,208,700,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2019-10142 | A flaw was found in the Linux kernel's freescale hypervisor manager implementation, kernel versions 5.0.x up to, excluding 5.0.17. A parameter passed to an ioctl was incorrectly validated and used in size calculations for the page size calculation. An attacker can use this flaw to crash the system, corrupt memory, or c... | https://nvd.nist.gov/vuln/detail/CVE-2019-10142 |
211,453 | hivex | 771728218dac2fbf6997a7e53225e75a4c6b7255 | https://github.com/libguestfs/hivex | https://github.com/libguestfs/hivex/commit/771728218dac2fbf6997a7e53225e75a4c6b7255 | lib/node.c: Limit recursion in ri-records (CVE-2021-3622)
Windows Registry hive "ri"-records are arbitrarily nested B-tree-like
structures:
+-------------+
| ri |
|-------------|
| nr_offsets |
| offset[0] ------> points to another lf/lh/li/ri block
| offset[1] ------>
| offset[2] -----... | 1 | _get_children (hive_h *h, hive_node_h blkoff,
offset_list *children, offset_list *blocks,
int flags)
{
/* Add this intermediate block. */
if (_hivex_add_to_offset_list (blocks, blkoff) == -1)
return -1;
struct ntreg_hbin_block *block =
(struct ntreg_hbin_block *) ((char *) h... | 214,527,172,131,826,930,000,000,000,000,000,000,000 | node.c | 197,906,538,220,370,870,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2021-3622 | A flaw was found in the hivex library. This flaw allows an attacker to input a specially crafted Windows Registry (hive) file, which would cause hivex to recursively call the _get_children() function, leading to a stack overflow. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3622 |
448,456 | hivex | 771728218dac2fbf6997a7e53225e75a4c6b7255 | https://github.com/libguestfs/hivex | https://github.com/libguestfs/hivex/commit/771728218dac2fbf6997a7e53225e75a4c6b7255 | lib/node.c: Limit recursion in ri-records (CVE-2021-3622)
Windows Registry hive "ri"-records are arbitrarily nested B-tree-like
structures:
+-------------+
| ri |
|-------------|
| nr_offsets |
| offset[0] ------> points to another lf/lh/li/ri block
| offset[1] ------>
| offset[2] -----... | 0 | _get_children (hive_h *h, hive_node_h blkoff,
offset_list *children, offset_list *blocks,
int flags, unsigned depth)
{
/* Add this intermediate block. */
if (_hivex_add_to_offset_list (blocks, blkoff) == -1)
return -1;
struct ntreg_hbin_block *block =
(struct ntreg_hbin_bloc... | 33,355,130,663,191,420,000,000,000,000,000,000,000 | node.c | 248,407,463,025,226,660,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2021-3622 | A flaw was found in the hivex library. This flaw allows an attacker to input a specially crafted Windows Registry (hive) file, which would cause hivex to recursively call the _get_children() function, leading to a stack overflow. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-3622 |
211,460 | libebml | ababb64e0c792ad2a314245233db0833ba12036b | https://github.com/Matroska-Org/libebml | https://github.com/Matroska-Org/libebml/commit/ababb64e0c792ad2a314245233db0833ba12036b | EbmlUnicodeString: don't read beyond end of string
The conversion from an UTF-8 encoded string into a wchar_t one was
reading from beyond the end of the source buffer if the length indicated
by a UTF-8 character's first byte exceeds the number of bytes actually
present afterwards.
Fixes the issue reported as Cisco TA... | 1 | void UTFstring::UpdateFromUTF8()
{
delete [] _Data;
// find the size of the final UCS-2 string
size_t i;
for (_Length=0, i=0; i<UTF8string.length(); _Length++) {
uint8 lead = static_cast<uint8>(UTF8string[i]);
if (lead < 0x80)
i++;
else if ((lead >> 5) == 0x6)
i += 2;
else if ((lead ... | 276,700,741,596,131,700,000,000,000,000,000,000,000 | EbmlUnicodeString.cpp | 307,679,874,427,603,980,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8790 | The EbmlUnicodeString::UpdateFromUTF8 function in libEBML before 1.3.3 allows context-dependent attackers to obtain sensitive information from process heap memory via a crafted UTF-8 string, which triggers an invalid memory access. | https://nvd.nist.gov/vuln/detail/CVE-2015-8790 |
448,485 | libebml | ababb64e0c792ad2a314245233db0833ba12036b | https://github.com/Matroska-Org/libebml | https://github.com/Matroska-Org/libebml/commit/ababb64e0c792ad2a314245233db0833ba12036b | EbmlUnicodeString: don't read beyond end of string
The conversion from an UTF-8 encoded string into a wchar_t one was
reading from beyond the end of the source buffer if the length indicated
by a UTF-8 character's first byte exceeds the number of bytes actually
present afterwards.
Fixes the issue reported as Cisco TA... | 0 | void UTFstring::UpdateFromUTF8()
{
delete [] _Data;
// find the size of the final UCS-2 string
size_t i;
const size_t SrcLength = UTF8string.length();
for (_Length=0, i=0; i<SrcLength; _Length++) {
const unsigned int CharLength = UTFCharLength(static_cast<uint8>(UTF8string[i]));
if ((CharLength >= 1) ... | 161,594,907,967,663,010,000,000,000,000,000,000,000 | EbmlUnicodeString.cpp | 308,407,556,256,610,400,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2015-8790 | The EbmlUnicodeString::UpdateFromUTF8 function in libEBML before 1.3.3 allows context-dependent attackers to obtain sensitive information from process heap memory via a crafted UTF-8 string, which triggers an invalid memory access. | https://nvd.nist.gov/vuln/detail/CVE-2015-8790 |
211,469 | Onigmo | 00cc7e28a3ed54b3b512ef3b58ea737a57acf1f9 | https://github.com/k-takata/Onigmo | https://github.com/k-takata/Onigmo/commit/00cc7e28a3ed54b3b512ef3b58ea737a57acf1f9 | Fix SEGV in onig_error_code_to_str() (Fix #132)
When onig_new(ONIG_SYNTAX_PERL) fails with ONIGERR_INVALID_GROUP_NAME,
onig_error_code_to_str() crashes.
onig_scan_env_set_error_string() should have been used when returning
ONIGERR_INVALID_GROUP_NAME. | 1 | fetch_token(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int r, num;
OnigCodePoint c;
OnigEncoding enc = env->enc;
const OnigSyntaxType* syn = env->syntax;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
start:
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
tok->type = TK_ST... | 102,312,851,319,520,690,000,000,000,000,000,000,000 | regparse.c | 124,494,677,407,376,820,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-16161 | Onigmo through 6.2.0 has a NULL pointer dereference in onig_error_code_to_str because of fetch_token in regparse.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-16161 |
448,524 | Onigmo | 00cc7e28a3ed54b3b512ef3b58ea737a57acf1f9 | https://github.com/k-takata/Onigmo | https://github.com/k-takata/Onigmo/commit/00cc7e28a3ed54b3b512ef3b58ea737a57acf1f9 | Fix SEGV in onig_error_code_to_str() (Fix #132)
When onig_new(ONIG_SYNTAX_PERL) fails with ONIGERR_INVALID_GROUP_NAME,
onig_error_code_to_str() crashes.
onig_scan_env_set_error_string() should have been used when returning
ONIGERR_INVALID_GROUP_NAME. | 0 | fetch_token(OnigToken* tok, UChar** src, UChar* end, ScanEnv* env)
{
int r, num;
OnigCodePoint c;
OnigEncoding enc = env->enc;
const OnigSyntaxType* syn = env->syntax;
UChar* prev;
UChar* p = *src;
PFETCH_READY;
start:
if (PEND) {
tok->type = TK_EOT;
return tok->type;
}
tok->type = TK_ST... | 254,075,013,594,164,640,000,000,000,000,000,000,000 | regparse.c | 52,848,815,961,077,240,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-16161 | Onigmo through 6.2.0 has a NULL pointer dereference in onig_error_code_to_str because of fetch_token in regparse.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-16161 |
211,482 | ImageMagick | 2c75f301d9ac84f91071393b02d8c88c8341c91c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/2c75f301d9ac84f91071393b02d8c88c8341c91c | https://github.com/ImageMagick/ImageMagick/issues/1225 | 1 | MagickExport const char *GetMagickProperty(ImageInfo *image_info,
Image *image,const char *property,ExceptionInfo *exception)
{
char
value[MagickPathExtent];
const char
*string;
assert(property[0] != '\0');
assert(image != (Image *) NULL || image_info != (ImageInfo *) NULL );
if (property[1] == '\... | 171,165,177,430,515,870,000,000,000,000,000,000,000 | property.c | 146,809,526,264,390,190,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-16329 | In ImageMagick before 7.0.8-8, a NULL pointer dereference exists in the GetMagickProperty function in MagickCore/property.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-16329 |
448,620 | ImageMagick | 2c75f301d9ac84f91071393b02d8c88c8341c91c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/2c75f301d9ac84f91071393b02d8c88c8341c91c | https://github.com/ImageMagick/ImageMagick/issues/1225 | 0 | MagickExport const char *GetMagickProperty(ImageInfo *image_info,
Image *image,const char *property,ExceptionInfo *exception)
{
char
value[MagickPathExtent];
const char
*string;
assert(property[0] != '\0');
assert(image != (Image *) NULL || image_info != (ImageInfo *) NULL );
if (property[1] == '\... | 207,841,334,286,166,250,000,000,000,000,000,000,000 | property.c | 93,256,489,230,441,080,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-16329 | In ImageMagick before 7.0.8-8, a NULL pointer dereference exists in the GetMagickProperty function in MagickCore/property.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-16329 |
211,499 | exim | 51be321b27825c01829dffd90f11bfff256f7e42 | https://github.com/Exim/exim | https://github.com/Exim/exim/commit/51be321b27825c01829dffd90f11bfff256f7e42 | Fix PAM auth. Bug 2813 | 1 | pam_converse (int num_msg, PAM_CONVERSE_ARG2_TYPE **msg,
struct pam_response **resp, void *appdata_ptr)
{
int sep = 0;
struct pam_response *reply;
/* It seems that PAM frees reply[] */
if ( pam_arg_ended
|| !(reply = malloc(sizeof(struct pam_response) * num_msg)))
return PAM_CONV_ERR;
for (int i = 0; i < num... | 284,828,868,281,264,840,000,000,000,000,000,000,000 | call_pam.c | 105,644,233,168,197,000,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2022-37451 | Exim before 4.96 has an invalid free in pam_converse in auths/call_pam.c because store_free is not used after store_malloc. | https://nvd.nist.gov/vuln/detail/CVE-2022-37451 |
448,745 | exim | 51be321b27825c01829dffd90f11bfff256f7e42 | https://github.com/Exim/exim | https://github.com/Exim/exim/commit/51be321b27825c01829dffd90f11bfff256f7e42 | Fix PAM auth. Bug 2813 | 0 | pam_converse (int num_msg, PAM_CONVERSE_ARG2_TYPE **msg,
struct pam_response **resp, void *appdata_ptr)
{
int sep = 0;
struct pam_response *reply;
/* It seems that PAM frees reply[] */
if ( pam_arg_ended
|| !(reply = malloc(sizeof(struct pam_response) * num_msg)))
return PAM_CONV_ERR;
for (int i = 0; i < num... | 119,469,198,695,581,900,000,000,000,000,000,000,000 | call_pam.c | 108,999,666,720,148,900,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2022-37451 | Exim before 4.96 has an invalid free in pam_converse in auths/call_pam.c because store_free is not used after store_malloc. | https://nvd.nist.gov/vuln/detail/CVE-2022-37451 |
211,501 | ImageMagick6 | 172d82afe89d3499ef0cab06dc58d380cc1ab946 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/172d82afe89d3499ef0cab06dc58d380cc1ab946 | https://github.com/ImageMagick/ImageMagick/issues/1149 | 1 | static Image *ReadMATImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image *image, *image2=NULL,
*rotated_image;
PixelPacket *q;
unsigned int status;
MATHeader MATLAB_HDR;
size_t size;
size_t CellType;
QuantumInfo *quantum_info;
ImageInfo *clone_info;
int i;
ssize_t ldblk;
unsign... | 64,224,352,703,038,360,000,000,000,000,000,000,000 | mat.c | 60,802,258,384,105,360,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-11624 | In ImageMagick 7.0.7-36 Q16, the ReadMATImage function in coders/mat.c allows attackers to cause a use after free via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11624 |
448,761 | ImageMagick6 | 172d82afe89d3499ef0cab06dc58d380cc1ab946 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/172d82afe89d3499ef0cab06dc58d380cc1ab946 | https://github.com/ImageMagick/ImageMagick/issues/1149 | 0 | static Image *ReadMATImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
Image *image, *image2=NULL,
*rotated_image;
PixelPacket *q;
unsigned int status;
MATHeader MATLAB_HDR;
size_t size;
size_t CellType;
QuantumInfo *quantum_info;
ImageInfo *clone_info;
int i;
ssize_t ldblk;
unsign... | 71,355,873,631,910,370,000,000,000,000,000,000,000 | mat.c | 147,863,288,409,532,070,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-11624 | In ImageMagick 7.0.7-36 Q16, the ReadMATImage function in coders/mat.c allows attackers to cause a use after free via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-11624 |
211,503 | php-src | 3804c0d00fa6e629173fb1c8c61f8f88d5fe39b9 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=3804c0d00fa6e629173fb1c8c61f8f88d5fe39b9 | Fix bug #67498 - phpinfo() Type Confusion Information Leak Vulnerability | 1 | */
PHPAPI void php_print_info(int flag TSRMLS_DC)
{
char **env, *tmp1, *tmp2;
char *php_uname;
if (!sapi_module.phpinfo_as_text) {
php_print_info_htmlhead(TSRMLS_C);
} else {
php_info_print("phpinfo()\n");
}
if (flag & PHP_INFO_GENERAL) {
char *zend_version = get_zend_version();
char temp_api[10];
p... | 19,114,472,618,640,646,000,000,000,000,000,000,000 | info.c | 135,939,357,707,428,830,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-4721 | The phpinfo implementation in ext/standard/info.c in PHP before 5.4.30 and 5.5.x before 5.5.14 does not ensure use of the string data type for the PHP_AUTH_PW, PHP_AUTH_TYPE, PHP_AUTH_USER, and PHP_SELF variables, which might allow context-dependent attackers to obtain sensitive information from process memory by using... | https://nvd.nist.gov/vuln/detail/CVE-2014-4721 |
448,893 | php-src | 3804c0d00fa6e629173fb1c8c61f8f88d5fe39b9 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=3804c0d00fa6e629173fb1c8c61f8f88d5fe39b9 | Fix bug #67498 - phpinfo() Type Confusion Information Leak Vulnerability | 0 | */
PHPAPI void php_print_info(int flag TSRMLS_DC)
{
char **env, *tmp1, *tmp2;
char *php_uname;
if (!sapi_module.phpinfo_as_text) {
php_print_info_htmlhead(TSRMLS_C);
} else {
php_info_print("phpinfo()\n");
}
if (flag & PHP_INFO_GENERAL) {
char *zend_version = get_zend_version();
char temp_api[10];
p... | 255,368,704,253,264,560,000,000,000,000,000,000,000 | info.c | 291,628,357,012,607,300,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-4721 | The phpinfo implementation in ext/standard/info.c in PHP before 5.4.30 and 5.5.x before 5.5.14 does not ensure use of the string data type for the PHP_AUTH_PW, PHP_AUTH_TYPE, PHP_AUTH_USER, and PHP_SELF variables, which might allow context-dependent attackers to obtain sensitive information from process memory by using... | https://nvd.nist.gov/vuln/detail/CVE-2014-4721 |
211,504 | glib | fccef3cc822af74699cca84cd202719ae61ca3b9 | https://gitlab.gnome.org/GNOME/glib | https://gitlab.gnome.org/GNOME/glib/commit/fccef3cc822af74699cca84cd202719ae61ca3b9 | gmarkup: Fix crash in error handling path for closing elements
If something which looks like a closing tag is left unfinished, but
isn’t paired to an opening tag in the document, the error handling code
would do a null pointer dereference. Avoid that, at the cost of
introducing a new translatable error message.
Inclu... | 1 | g_markup_parse_context_end_parse (GMarkupParseContext *context,
GError **error)
{
g_return_val_if_fail (context != NULL, FALSE);
g_return_val_if_fail (!context->parsing, FALSE);
g_return_val_if_fail (context->state != STATE_ERROR, FALSE);
if (context->partial_chu... | 260,116,118,098,812,700,000,000,000,000,000,000,000 | gmarkup.c | 321,830,226,907,327,630,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-16428 | In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2018-16428 |
448,909 | glib | fccef3cc822af74699cca84cd202719ae61ca3b9 | https://gitlab.gnome.org/GNOME/glib | https://gitlab.gnome.org/GNOME/glib/commit/fccef3cc822af74699cca84cd202719ae61ca3b9 | gmarkup: Fix crash in error handling path for closing elements
If something which looks like a closing tag is left unfinished, but
isn’t paired to an opening tag in the document, the error handling code
would do a null pointer dereference. Avoid that, at the cost of
introducing a new translatable error message.
Inclu... | 0 | g_markup_parse_context_end_parse (GMarkupParseContext *context,
GError **error)
{
g_return_val_if_fail (context != NULL, FALSE);
g_return_val_if_fail (!context->parsing, FALSE);
g_return_val_if_fail (context->state != STATE_ERROR, FALSE);
if (context->partial_chu... | 308,666,615,377,585,100,000,000,000,000,000,000,000 | gmarkup.c | 25,355,892,022,694,536,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-16428 | In GNOME GLib 2.56.1, g_markup_parse_context_end_parse() in gmarkup.c has a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2018-16428 |
211,510 | linux | c364df2489b8ef2f5e3159b1dff1ff1fdb16040d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c364df2489b8ef2f5e3159b1dff1ff1fdb16040d | net: ll_temac: Fix TX BD buffer overwrite
Just as the initial check, we need to ensure num_frag+1 buffers available,
as that is the number of buffers we are going to use.
This fixes a buffer overflow, which might be seen during heavy network
load. Complete lockup of TEMAC was reproducible within about 10 minutes of
a... | 1 | temac_start_xmit(struct sk_buff *skb, struct net_device *ndev)
{
struct temac_local *lp = netdev_priv(ndev);
struct cdmac_bd *cur_p;
dma_addr_t tail_p, skb_dma_addr;
int ii;
unsigned long num_frag;
skb_frag_t *frag;
num_frag = skb_shinfo(skb)->nr_frags;
frag = &skb_shinfo(skb)->frags[0];
cur_p = &lp->tx_bd_v[... | 193,504,278,803,094,900,000,000,000,000,000,000,000 | ll_temac_main.c | 16,737,093,425,407,387,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-38207 | drivers/net/ethernet/xilinx/ll_temac_main.c in the Linux kernel before 5.12.13 allows remote attackers to cause a denial of service (buffer overflow and lockup) by sending heavy network traffic for about ten minutes. | https://nvd.nist.gov/vuln/detail/CVE-2021-38207 |
448,948 | linux | c364df2489b8ef2f5e3159b1dff1ff1fdb16040d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c364df2489b8ef2f5e3159b1dff1ff1fdb16040d | net: ll_temac: Fix TX BD buffer overwrite
Just as the initial check, we need to ensure num_frag+1 buffers available,
as that is the number of buffers we are going to use.
This fixes a buffer overflow, which might be seen during heavy network
load. Complete lockup of TEMAC was reproducible within about 10 minutes of
a... | 0 | temac_start_xmit(struct sk_buff *skb, struct net_device *ndev)
{
struct temac_local *lp = netdev_priv(ndev);
struct cdmac_bd *cur_p;
dma_addr_t tail_p, skb_dma_addr;
int ii;
unsigned long num_frag;
skb_frag_t *frag;
num_frag = skb_shinfo(skb)->nr_frags;
frag = &skb_shinfo(skb)->frags[0];
cur_p = &lp->tx_bd_v[... | 53,541,701,122,900,630,000,000,000,000,000,000,000 | ll_temac_main.c | 201,637,401,286,691,880,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-38207 | drivers/net/ethernet/xilinx/ll_temac_main.c in the Linux kernel before 5.12.13 allows remote attackers to cause a denial of service (buffer overflow and lockup) by sending heavy network traffic for about ten minutes. | https://nvd.nist.gov/vuln/detail/CVE-2021-38207 |
211,560 | libgit2 | 3f7851eadca36a99627ad78cbe56a40d3776ed01 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/3f7851eadca36a99627ad78cbe56a40d3776ed01 | Disallow NTFS Alternate Data Stream attacks, even on Linux/macOS
A little-known feature of NTFS is that it offers to store metadata in
so-called "Alternate Data Streams" (inspired by Apple's "resource
forks") that are copied together with the file they are associated with.
These Alternate Data Streams can be accessed ... | 1 | GIT_INLINE(bool) verify_dotgit_ntfs(git_repository *repo, const char *path, size_t len)
{
git_buf *reserved = git_repository__reserved_names_win32;
size_t reserved_len = git_repository__reserved_names_win32_len;
size_t start = 0, i;
if (repo)
git_repository__reserved_names(&reserved, &reserved_len, repo, true);
... | 64,009,400,043,272,730,000,000,000,000,000,000,000 | path.c | 318,398,333,848,559,040,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-12278 | An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when cloning a repository. This issue is similar to CVE-2019-1352. | https://nvd.nist.gov/vuln/detail/CVE-2020-12278 |
449,264 | libgit2 | 3f7851eadca36a99627ad78cbe56a40d3776ed01 | https://github.com/libgit2/libgit2 | https://github.com/libgit2/libgit2/commit/3f7851eadca36a99627ad78cbe56a40d3776ed01 | Disallow NTFS Alternate Data Stream attacks, even on Linux/macOS
A little-known feature of NTFS is that it offers to store metadata in
so-called "Alternate Data Streams" (inspired by Apple's "resource
forks") that are copied together with the file they are associated with.
These Alternate Data Streams can be accessed ... | 0 | GIT_INLINE(bool) verify_dotgit_ntfs(git_repository *repo, const char *path, size_t len)
{
git_buf *reserved = git_repository__reserved_names_win32;
size_t reserved_len = git_repository__reserved_names_win32_len;
size_t start = 0, i;
if (repo)
git_repository__reserved_names(&reserved, &reserved_len, repo, true);
... | 131,230,699,596,049,340,000,000,000,000,000,000,000 | path.c | 135,494,464,199,321,380,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-12278 | An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when cloning a repository. This issue is similar to CVE-2019-1352. | https://nvd.nist.gov/vuln/detail/CVE-2020-12278 |
211,561 | mutt | 7c4779ac24d2fb68a2a47b58c7904118f40965d5 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/-/commit/7c4779ac24d2fb68a2a47b58c7904118f40965d5 | Fix seqset iterator when it ends in a comma.
If the seqset ended with a comma, the substr_end marker would be just
before the trailing nul. In the next call, the loop to skip the
marker would iterate right past the end of string too.
The fix is simple: place the substr_end marker and skip past it
immediately. | 1 | int mutt_seqset_iterator_next (SEQSET_ITERATOR *iter, unsigned int *next)
{
char *range_sep;
if (!iter || !next)
return -1;
if (iter->in_range)
{
if ((iter->down && iter->range_cur == (iter->range_end - 1)) ||
(!iter->down && iter->range_cur == (iter->range_end + 1)))
iter->in_range = 0;... | 297,848,409,410,886,640,000,000,000,000,000,000,000 | util.c | 15,446,244,465,856,450,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2021-32055 | Mutt 1.11.0 through 2.0.x before 2.0.7 (and NeoMutt 2019-10-25 through 2021-05-04) has a $imap_qresync issue in which imap/util.c has an out-of-bounds read in situations where an IMAP sequence set ends with a comma. NOTE: the $imap_qresync setting for QRESYNC is not enabled by default. | https://nvd.nist.gov/vuln/detail/CVE-2021-32055 |
449,284 | mutt | 7c4779ac24d2fb68a2a47b58c7904118f40965d5 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/-/commit/7c4779ac24d2fb68a2a47b58c7904118f40965d5 | Fix seqset iterator when it ends in a comma.
If the seqset ended with a comma, the substr_end marker would be just
before the trailing nul. In the next call, the loop to skip the
marker would iterate right past the end of string too.
The fix is simple: place the substr_end marker and skip past it
immediately. | 0 | int mutt_seqset_iterator_next (SEQSET_ITERATOR *iter, unsigned int *next)
{
char *range_sep;
if (!iter || !next)
return -1;
if (iter->in_range)
{
if ((iter->down && iter->range_cur == (iter->range_end - 1)) ||
(!iter->down && iter->range_cur == (iter->range_end + 1)))
iter->in_range = 0;... | 156,834,549,562,274,340,000,000,000,000,000,000,000 | util.c | 297,145,212,288,974,650,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2021-32055 | Mutt 1.11.0 through 2.0.x before 2.0.7 (and NeoMutt 2019-10-25 through 2021-05-04) has a $imap_qresync issue in which imap/util.c has an out-of-bounds read in situations where an IMAP sequence set ends with a comma. NOTE: the $imap_qresync setting for QRESYNC is not enabled by default. | https://nvd.nist.gov/vuln/detail/CVE-2021-32055 |
211,562 | pango | 490f8979a260c16b1df055eab386345da18a2d54 | http://github.com/bratsche/pango | https://gitlab.gnome.org/GNOME/pango/commit/490f8979a260c16b1df055eab386345da18a2d54 | bidi: Be safer against bad input
Don't run off the end of an array that we
allocated to certain length.
Closes: https://gitlab.gnome.org/GNOME/pango/issues/342 | 1 | pango_log2vis_get_embedding_levels (const gchar *text,
int length,
PangoDirection *pbase_dir)
{
glong n_chars, i;
guint8 *embedding_levels_list;
const gchar *p;
FriBidiParType fribidi_base_dir;
FriBidiCharType *bidi_types;
#ifdef USE_FRIBIDI_EX_API
FriBidiBracketType *bracket_... | 197,927,692,778,166,860,000,000,000,000,000,000,000 | pango-bidi-type.c | 298,741,540,084,538,100,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-1010238 | Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass inval... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010238 |
449,289 | pango | 490f8979a260c16b1df055eab386345da18a2d54 | http://github.com/bratsche/pango | https://gitlab.gnome.org/GNOME/pango/commit/490f8979a260c16b1df055eab386345da18a2d54 | bidi: Be safer against bad input
Don't run off the end of an array that we
allocated to certain length.
Closes: https://gitlab.gnome.org/GNOME/pango/issues/342 | 0 | pango_log2vis_get_embedding_levels (const gchar *text,
int length,
PangoDirection *pbase_dir)
{
glong n_chars, i;
guint8 *embedding_levels_list;
const gchar *p;
FriBidiParType fribidi_base_dir;
FriBidiCharType *bidi_types;
#ifdef USE_FRIBIDI_EX_API
FriBidiBracketType *bracket_... | 180,043,076,199,475,700,000,000,000,000,000,000,000 | pango-bidi-type.c | 218,096,712,748,954,350,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-1010238 | Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass inval... | https://nvd.nist.gov/vuln/detail/CVE-2019-1010238 |
211,586 | mupdf | 60dabde18d7fe12b19da8b509bdfee9cc886aafc | https://github.com/ArtifexSoftware/mupdf | http://git.ghostscript.com/?p=mupdf.git;a=commitdiff;h=60dabde18d7fe12b19da8b509bdfee9cc886aafc | Bug 694957: fix stack buffer overflow in xps_parse_color
xps_parse_color happily reads more than FZ_MAX_COLORS values out of a
ContextColor array which overflows the passed in samples array.
Limiting the number of allowed samples to FZ_MAX_COLORS and make sure
to use that constant for all callers fixes the problem.
T... | 1 | xps_parse_color(xps_document *doc, char *base_uri, char *string,
fz_colorspace **csp, float *samples)
{
char *p;
int i, n;
char buf[1024];
char *profile;
*csp = fz_device_rgb(doc->ctx);
samples[0] = 1;
samples[1] = 0;
samples[2] = 0;
samples[3] = 0;
if (string[0] == '#')
{
if (strlen(string) == 9)
{... | 36,382,987,661,250,006,000,000,000,000,000,000,000 | xps-common.c | 257,813,168,722,929,430,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-2013 | Stack-based buffer overflow in the xps_parse_color function in xps/xps-common.c in MuPDF 1.3 and earlier allows remote attackers to execute arbitrary code via a large number of entries in the ContextColor value of the Fill attribute in a Path element. | https://nvd.nist.gov/vuln/detail/CVE-2014-2013 |
449,462 | mupdf | 60dabde18d7fe12b19da8b509bdfee9cc886aafc | https://github.com/ArtifexSoftware/mupdf | http://git.ghostscript.com/?p=mupdf.git;a=commitdiff;h=60dabde18d7fe12b19da8b509bdfee9cc886aafc | Bug 694957: fix stack buffer overflow in xps_parse_color
xps_parse_color happily reads more than FZ_MAX_COLORS values out of a
ContextColor array which overflows the passed in samples array.
Limiting the number of allowed samples to FZ_MAX_COLORS and make sure
to use that constant for all callers fixes the problem.
T... | 0 | xps_parse_color(xps_document *doc, char *base_uri, char *string,
fz_colorspace **csp, float *samples)
{
fz_context *ctx = doc->ctx;
char *p;
int i, n;
char buf[1024];
char *profile;
*csp = fz_device_rgb(ctx);
samples[0] = 1;
samples[1] = 0;
samples[2] = 0;
samples[3] = 0;
if (string[0] == '#')
{
if (... | 329,640,994,680,338,140,000,000,000,000,000,000,000 | xps-common.c | 165,036,389,961,832,330,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-2013 | Stack-based buffer overflow in the xps_parse_color function in xps/xps-common.c in MuPDF 1.3 and earlier allows remote attackers to execute arbitrary code via a large number of entries in the ContextColor value of the Fill attribute in a Path element. | https://nvd.nist.gov/vuln/detail/CVE-2014-2013 |
211,588 | qemu | 141b197408ab398c4f474ac1a728ab316e921f2b | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=141b197408ab398c4f474ac1a728ab316e921f2b | qga: check bytes count read by guest-file-read
While reading file content via 'guest-file-read' command,
'qmp_guest_file_read' routine allocates buffer of count+1
bytes. It could overflow for large values of 'count'.
Add check to avoid it.
Reported-by: Fakhri Zulkifli <mohdfakhrizulkifli@gmail.com>
Signed-off-by: Pra... | 1 | struct GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
int64_t count, Error **errp)
{
GuestFileHandle *gfh = guest_file_handle_find(handle, errp);
GuestFileRead *read_data = NULL;
guchar *buf;
FILE *fh;
size_t read_count;
if (!gfh) {
... | 327,793,751,593,432,700,000,000,000,000,000,000,000 | commands-posix.c | 34,722,710,308,995,996,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-12617 | qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP command (inc... | https://nvd.nist.gov/vuln/detail/CVE-2018-12617 |
449,598 | qemu | 141b197408ab398c4f474ac1a728ab316e921f2b | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=141b197408ab398c4f474ac1a728ab316e921f2b | qga: check bytes count read by guest-file-read
While reading file content via 'guest-file-read' command,
'qmp_guest_file_read' routine allocates buffer of count+1
bytes. It could overflow for large values of 'count'.
Add check to avoid it.
Reported-by: Fakhri Zulkifli <mohdfakhrizulkifli@gmail.com>
Signed-off-by: Pra... | 0 | struct GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
int64_t count, Error **errp)
{
GuestFileHandle *gfh = guest_file_handle_find(handle, errp);
GuestFileRead *read_data = NULL;
guchar *buf;
FILE *fh;
size_t read_count;
if (!gfh) {
... | 263,536,644,974,258,400,000,000,000,000,000,000,000 | commands-posix.c | 24,392,814,676,123,963,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-12617 | qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP command (inc... | https://nvd.nist.gov/vuln/detail/CVE-2018-12617 |
211,589 | qemu | 141b197408ab398c4f474ac1a728ab316e921f2b | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=141b197408ab398c4f474ac1a728ab316e921f2b | qga: check bytes count read by guest-file-read
While reading file content via 'guest-file-read' command,
'qmp_guest_file_read' routine allocates buffer of count+1
bytes. It could overflow for large values of 'count'.
Add check to avoid it.
Reported-by: Fakhri Zulkifli <mohdfakhrizulkifli@gmail.com>
Signed-off-by: Pra... | 1 | GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
int64_t count, Error **errp)
{
GuestFileRead *read_data = NULL;
guchar *buf;
HANDLE fh;
bool is_ok;
DWORD read_count;
GuestFileHandle *gfh = guest_file_handle_find(handle, errp);
if (!gfh) ... | 51,522,177,041,267,490,000,000,000,000,000,000,000 | commands-win32.c | 336,033,201,079,126,800,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-12617 | qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP command (inc... | https://nvd.nist.gov/vuln/detail/CVE-2018-12617 |
449,587 | qemu | 141b197408ab398c4f474ac1a728ab316e921f2b | https://github.com/bonzini/qemu | https://git.qemu.org/?p=qemu.git;a=commit;h=141b197408ab398c4f474ac1a728ab316e921f2b | qga: check bytes count read by guest-file-read
While reading file content via 'guest-file-read' command,
'qmp_guest_file_read' routine allocates buffer of count+1
bytes. It could overflow for large values of 'count'.
Add check to avoid it.
Reported-by: Fakhri Zulkifli <mohdfakhrizulkifli@gmail.com>
Signed-off-by: Pra... | 0 | GuestFileRead *qmp_guest_file_read(int64_t handle, bool has_count,
int64_t count, Error **errp)
{
GuestFileRead *read_data = NULL;
guchar *buf;
HANDLE fh;
bool is_ok;
DWORD read_count;
GuestFileHandle *gfh = guest_file_handle_find(handle, errp);
if (!gfh) ... | 162,130,526,146,268,480,000,000,000,000,000,000,000 | commands-win32.c | 121,724,615,210,967,120,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2018-12617 | qmp_guest_file_read in qga/commands-posix.c and qga/commands-win32.c in qemu-ga (aka QEMU Guest Agent) in QEMU 2.12.50 has an integer overflow causing a g_malloc0() call to trigger a segmentation fault when trying to allocate a large memory chunk. The vulnerability can be exploited by sending a crafted QMP command (inc... | https://nvd.nist.gov/vuln/detail/CVE-2018-12617 |
211,651 | poppler | 27354e9d9696ee2bc063910a6c9a6b27c5184a52 | https://github.com/freedesktop/poppler | https://github.com/freedesktop/poppler/commit/27354e9d9696ee2bc063910a6c9a6b27c5184a52 | JBIG2Stream: Fix crash on broken file
https://github.com/jeffssh/CVE-2021-30860
Thanks to David Warren for the heads up | 1 | void JBIG2Stream::readTextRegionSeg(unsigned int segNum, bool imm, bool lossless, unsigned int length, unsigned int *refSegs, unsigned int nRefSegs)
{
std::unique_ptr<JBIG2Bitmap> bitmap;
JBIG2HuffmanTable runLengthTab[36];
JBIG2HuffmanTable *symCodeTab = nullptr;
const JBIG2HuffmanTable *huffFSTable, *... | 182,517,253,860,179,970,000,000,000,000,000,000,000 | JBIG2Stream.cc | 156,076,935,461,444,860,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-38784 | Poppler prior to and including 22.08.0 contains an integer overflow in the JBIG2 decoder (JBIG2Stream::readTextRegionSeg() in JBIGStream.cc). Processing a specially crafted PDF file or JBIG2 image could lead to a crash or the execution of arbitrary code. This is similar to the vulnerability described by CVE-2022-38171 ... | https://nvd.nist.gov/vuln/detail/CVE-2022-38784 |
450,271 | poppler | 27354e9d9696ee2bc063910a6c9a6b27c5184a52 | https://github.com/freedesktop/poppler | https://github.com/freedesktop/poppler/commit/27354e9d9696ee2bc063910a6c9a6b27c5184a52 | JBIG2Stream: Fix crash on broken file
https://github.com/jeffssh/CVE-2021-30860
Thanks to David Warren for the heads up | 0 | void JBIG2Stream::readTextRegionSeg(unsigned int segNum, bool imm, bool lossless, unsigned int length, unsigned int *refSegs, unsigned int nRefSegs)
{
std::unique_ptr<JBIG2Bitmap> bitmap;
JBIG2HuffmanTable runLengthTab[36];
JBIG2HuffmanTable *symCodeTab = nullptr;
const JBIG2HuffmanTable *huffFSTable, *... | 296,879,935,704,981,950,000,000,000,000,000,000,000 | JBIG2Stream.cc | 192,778,333,266,759,250,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-38784 | Poppler prior to and including 22.08.0 contains an integer overflow in the JBIG2 decoder (JBIG2Stream::readTextRegionSeg() in JBIGStream.cc). Processing a specially crafted PDF file or JBIG2 image could lead to a crash or the execution of arbitrary code. This is similar to the vulnerability described by CVE-2022-38171 ... | https://nvd.nist.gov/vuln/detail/CVE-2022-38784 |
211,694 | linux | 27d461333459d282ffa4a2bdb6b215a59d493a8f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27d461333459d282ffa4a2bdb6b215a59d493a8f | i40e: prevent memory leak in i40e_setup_macvlans
In i40e_setup_macvlans if i40e_setup_channel fails the allocated memory
for ch should be released.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 1 | static int i40e_setup_macvlans(struct i40e_vsi *vsi, u16 macvlan_cnt, u16 qcnt,
struct net_device *vdev)
{
struct i40e_pf *pf = vsi->back;
struct i40e_hw *hw = &pf->hw;
struct i40e_vsi_context ctxt;
u16 sections, qmap, num_qps;
struct i40e_channel *ch;
int i, pow, ret = 0;
u8 offset = 0;
if (vsi->typ... | 221,953,846,027,087,400,000,000,000,000,000,000,000 | i40e_main.c | 308,331,918,161,742,340,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19043 | A memory leak in the i40e_setup_macvlans() function in drivers/net/ethernet/intel/i40e/i40e_main.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering i40e_setup_channel() failures, aka CID-27d461333459. | https://nvd.nist.gov/vuln/detail/CVE-2019-19043 |
450,626 | linux | 27d461333459d282ffa4a2bdb6b215a59d493a8f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/27d461333459d282ffa4a2bdb6b215a59d493a8f | i40e: prevent memory leak in i40e_setup_macvlans
In i40e_setup_macvlans if i40e_setup_channel fails the allocated memory
for ch should be released.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 0 | static int i40e_setup_macvlans(struct i40e_vsi *vsi, u16 macvlan_cnt, u16 qcnt,
struct net_device *vdev)
{
struct i40e_pf *pf = vsi->back;
struct i40e_hw *hw = &pf->hw;
struct i40e_vsi_context ctxt;
u16 sections, qmap, num_qps;
struct i40e_channel *ch;
int i, pow, ret = 0;
u8 offset = 0;
if (vsi->typ... | 207,780,618,832,738,680,000,000,000,000,000,000,000 | i40e_main.c | 288,123,846,412,478,960,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19043 | A memory leak in the i40e_setup_macvlans() function in drivers/net/ethernet/intel/i40e/i40e_main.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering i40e_setup_channel() failures, aka CID-27d461333459. | https://nvd.nist.gov/vuln/detail/CVE-2019-19043 |
211,703 | unbound | 09707fc403a7e0d7f5ef0029c597c2645ba49dd5 | https://github.com/NLnetLabs/unbound | https://github.com/NLnetLabs/unbound/commit/09707fc403a7e0d7f5ef0029c597c2645ba49dd5 | - Fix Integer Underflow in Regional Allocator,
reported by X41 D-Sec. | 1 | regional_create_custom(size_t size)
{
struct regional* r = (struct regional*)malloc(size);
log_assert(sizeof(struct regional) <= size);
if(!r) return NULL;
r->first_size = size;
regional_init(r);
return r;
} | 300,782,657,527,805,800,000,000,000,000,000,000,000 | regional.c | 210,699,362,817,104,200,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-25033 | Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro. NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound installation cannot be remotely or locally exploited | https://nvd.nist.gov/vuln/detail/CVE-2019-25033 |
450,836 | unbound | 09707fc403a7e0d7f5ef0029c597c2645ba49dd5 | https://github.com/NLnetLabs/unbound | https://github.com/NLnetLabs/unbound/commit/09707fc403a7e0d7f5ef0029c597c2645ba49dd5 | - Fix Integer Underflow in Regional Allocator,
reported by X41 D-Sec. | 0 | regional_create_custom(size_t size)
{
struct regional* r = (struct regional*)malloc(size);
size = ALIGN_UP(size, ALIGNMENT);
log_assert(sizeof(struct regional) <= size);
if(!r) return NULL;
r->first_size = size;
regional_init(r);
return r;
} | 319,232,279,593,715,070,000,000,000,000,000,000,000 | regional.c | 233,996,396,084,330,750,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2019-25033 | Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro. NOTE: The vendor disputes that this is a vulnerability. Although the code may be vulnerable, a running Unbound installation cannot be remotely or locally exploited | https://nvd.nist.gov/vuln/detail/CVE-2019-25033 |
211,714 | ZRTPCPP | c8617100f359b217a974938c5539a1dd8a120b0e | https://github.com/wernerd/ZRTPCPP | https://github.com/wernerd/ZRTPCPP/commit/c8617100f359b217a974938c5539a1dd8a120b0e | Fix vulnerabilities found and reported by Mark Dowd
- limit length of memcpy
- limit number of offered algorithms in Hello packet
- length check in PING packet
- fix a small coding error | 1 | void ZRtp::storeMsgTemp(ZrtpPacketBase* pkt) {
int32_t length = pkt->getLength() * ZRTP_WORD_SIZE;
memset(tempMsgBuffer, 0, sizeof(tempMsgBuffer));
memcpy(tempMsgBuffer, (uint8_t*)pkt->getHeaderBase(), length);
lengthOfMsgData = length;
} | 266,270,527,793,675,070,000,000,000,000,000,000,000 | ZRtp.cpp | 24,353,967,727,623,513,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2221 | Heap-based buffer overflow in the ZRtp::storeMsgTemp function in GNU ZRTPCPP before 3.2.0 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-2221 |
450,909 | ZRTPCPP | c8617100f359b217a974938c5539a1dd8a120b0e | https://github.com/wernerd/ZRTPCPP | https://github.com/wernerd/ZRTPCPP/commit/c8617100f359b217a974938c5539a1dd8a120b0e | Fix vulnerabilities found and reported by Mark Dowd
- limit length of memcpy
- limit number of offered algorithms in Hello packet
- length check in PING packet
- fix a small coding error | 0 | void ZRtp::storeMsgTemp(ZrtpPacketBase* pkt) {
uint32_t length = pkt->getLength() * ZRTP_WORD_SIZE;
length = (length > sizeof(tempMsgBuffer)) ? sizeof(tempMsgBuffer) : length;
memset(tempMsgBuffer, 0, sizeof(tempMsgBuffer));
memcpy(tempMsgBuffer, (uint8_t*)pkt->getHeaderBase(), length);
lengthOfMsgD... | 283,033,657,245,639,370,000,000,000,000,000,000,000 | ZRtp.cpp | 164,259,973,784,313,340,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-2221 | Heap-based buffer overflow in the ZRtp::storeMsgTemp function in GNU ZRTPCPP before 3.2.0 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large packet. | https://nvd.nist.gov/vuln/detail/CVE-2013-2221 |
211,716 | LibRaw | c14ae36d28e80139b2f31b5d9d7623db3b597a3a | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/c14ae36d28e80139b2f31b5d9d7623db3b597a3a | fixed error handling for broken full-color images | 1 | int LibRaw::unpack(void)
{
CHECK_ORDER_HIGH(LIBRAW_PROGRESS_LOAD_RAW);
CHECK_ORDER_LOW(LIBRAW_PROGRESS_IDENTIFY);
try {
RUN_CALLBACK(LIBRAW_PROGRESS_LOAD_RAW,0,2);
if (O.shot_select >= P1.raw_count)
return LIBRAW_REQUEST_FOR_NONEXISTENT_IMAGE;
if(!load_raw)
... | 302,109,011,717,818,930,000,000,000,000,000,000,000 | libraw_cxx.cpp | 78,682,339,942,612,800,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2126 | Multiple double free vulnerabilities in the LibRaw::unpack function in libraw_cxx.cpp in LibRaw before 0.15.2 allow context-dependent attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a malformed full-color (1) Foveon or (2) sRAW image file. | https://nvd.nist.gov/vuln/detail/CVE-2013-2126 |
451,088 | LibRaw | c14ae36d28e80139b2f31b5d9d7623db3b597a3a | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/c14ae36d28e80139b2f31b5d9d7623db3b597a3a | fixed error handling for broken full-color images | 0 | int LibRaw::unpack(void)
{
CHECK_ORDER_HIGH(LIBRAW_PROGRESS_LOAD_RAW);
CHECK_ORDER_LOW(LIBRAW_PROGRESS_IDENTIFY);
try {
RUN_CALLBACK(LIBRAW_PROGRESS_LOAD_RAW,0,2);
if (O.shot_select >= P1.raw_count)
return LIBRAW_REQUEST_FOR_NONEXISTENT_IMAGE;
if(!load_raw)
... | 19,151,301,484,341,342,000,000,000,000,000,000,000 | libraw_cxx.cpp | 134,474,915,560,578,790,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-2126 | Multiple double free vulnerabilities in the LibRaw::unpack function in libraw_cxx.cpp in LibRaw before 0.15.2 allow context-dependent attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a malformed full-color (1) Foveon or (2) sRAW image file. | https://nvd.nist.gov/vuln/detail/CVE-2013-2126 |
211,717 | vim | d0b5138ba4bccff8a744c99836041ef6322ed39a | https://github.com/vim/vim | https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | patch 8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'. | 1 | did_set_string_option(
int opt_idx, /* index in options[] table */
char_u **varp, /* pointer to the option variable */
int new_value_alloced, /* new value was allocated */
char_u *oldval, /* previous value of the option */
char_u *errbuf, /* buffer for errors, or NULL */
int opt_flags) ... | 179,532,119,812,438,600,000,000,000,000,000,000,000 | option.c | 74,593,441,812,466,570,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
451,172 | vim | d0b5138ba4bccff8a744c99836041ef6322ed39a | https://github.com/vim/vim | https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | patch 8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'. | 0 | did_set_string_option(
int opt_idx, /* index in options[] table */
char_u **varp, /* pointer to the option variable */
int new_value_alloced, /* new value was allocated */
char_u *oldval, /* previous value of the option */
char_u *errbuf, /* buffer for errors, or NULL */
int opt_flags) ... | 233,529,390,265,990,500,000,000,000,000,000,000,000 | option.c | 96,567,048,204,708,920,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-1248 | vim before patch 8.0.0056 does not properly validate values for the 'filetype', 'syntax' and 'keymap' options, which may result in the execution of arbitrary code if a file with a specially crafted modeline is opened. | https://nvd.nist.gov/vuln/detail/CVE-2016-1248 |
211,718 | linux | e7af6307a8a54f0b873960b32b6a644f2d0fbd97 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e7af6307a8a54f0b873960b32b6a644f2d0fbd97 | ALSA: timer: Fix incorrectly assigned timer instance
The clean up commit 41672c0c24a6 ("ALSA: timer: Simplify error path in
snd_timer_open()") unified the error handling code paths with the
standard goto, but it introduced a subtle bug: the timer instance is
stored in snd_timer_open() incorrectly even if it returns an... | 1 | int snd_timer_open(struct snd_timer_instance **ti,
char *owner, struct snd_timer_id *tid,
unsigned int slave_id)
{
struct snd_timer *timer;
struct snd_timer_instance *timeri = NULL;
struct device *card_dev_to_put = NULL;
int err;
mutex_lock(®ister_mutex);
if (tid->dev_class == SNDRV_TIMER_CLASS_SLAV... | 33,167,892,918,644,720,000,000,000,000,000,000,000 | timer.c | 167,246,863,290,195,860,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19807 | In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for a different purpose ... | https://nvd.nist.gov/vuln/detail/CVE-2019-19807 |
451,209 | linux | e7af6307a8a54f0b873960b32b6a644f2d0fbd97 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e7af6307a8a54f0b873960b32b6a644f2d0fbd97 | ALSA: timer: Fix incorrectly assigned timer instance
The clean up commit 41672c0c24a6 ("ALSA: timer: Simplify error path in
snd_timer_open()") unified the error handling code paths with the
standard goto, but it introduced a subtle bug: the timer instance is
stored in snd_timer_open() incorrectly even if it returns an... | 0 | int snd_timer_open(struct snd_timer_instance **ti,
char *owner, struct snd_timer_id *tid,
unsigned int slave_id)
{
struct snd_timer *timer;
struct snd_timer_instance *timeri = NULL;
struct device *card_dev_to_put = NULL;
int err;
mutex_lock(®ister_mutex);
if (tid->dev_class == SNDRV_TIMER_CLASS_SLAV... | 255,200,782,188,459,650,000,000,000,000,000,000,000 | timer.c | 244,534,628,575,940,640,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19807 | In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for a different purpose ... | https://nvd.nist.gov/vuln/detail/CVE-2019-19807 |
211,727 | sudo | b301b46b79c6e2a76d530fa36d05992e74952ee8 | https://github.com/sudo-project/sudo | https://github.com/sudo-project/sudo/commit/b301b46b79c6e2a76d530fa36d05992e74952ee8 | Reset valid_flags to MODE_NONINTERACTIVE for sudoedit.
This is consistent with how the -e option is handled.
Also reject -H and -P flags for sudoedit as was done in sudo 1.7.
Found by Qualys, this is part of the fix for CVE-2021-3156. | 1 | parse_args(int argc, char **argv, int *old_optind, int *nargc, char ***nargv,
struct sudo_settings **settingsp, char ***env_addp)
{
struct environment extra_env;
int mode = 0; /* what mode is sudo to be run in? */
int flags = 0; /* mode flags */
int valid_flags = DEFAULT_VALID_FLAGS;
int ch, i... | 24,032,268,513,571,147,000,000,000,000,000,000,000 | parse_args.c | 221,940,753,376,398,040,000,000,000,000,000,000,000 | [
"CWE-193"
] | CVE-2021-3156 | Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root via "sudoedit -s" and a command-line argument that ends with a single backslash character. | https://nvd.nist.gov/vuln/detail/CVE-2021-3156 |
451,318 | sudo | b301b46b79c6e2a76d530fa36d05992e74952ee8 | https://github.com/sudo-project/sudo | https://github.com/sudo-project/sudo/commit/b301b46b79c6e2a76d530fa36d05992e74952ee8 | Reset valid_flags to MODE_NONINTERACTIVE for sudoedit.
This is consistent with how the -e option is handled.
Also reject -H and -P flags for sudoedit as was done in sudo 1.7.
Found by Qualys, this is part of the fix for CVE-2021-3156. | 0 | parse_args(int argc, char **argv, int *old_optind, int *nargc, char ***nargv,
struct sudo_settings **settingsp, char ***env_addp)
{
struct environment extra_env;
int mode = 0; /* what mode is sudo to be run in? */
int flags = 0; /* mode flags */
int valid_flags = DEFAULT_VALID_FLAGS;
int ch, i... | 160,226,436,482,935,430,000,000,000,000,000,000,000 | parse_args.c | 8,211,792,186,095,039,000,000,000,000,000,000,000 | [
"CWE-193"
] | CVE-2021-3156 | Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root via "sudoedit -s" and a command-line argument that ends with a single backslash character. | https://nvd.nist.gov/vuln/detail/CVE-2021-3156 |
211,728 | libreswan | 471a3e41a449d7c753bc4edbba4239501bb62ba8 | https://github.com/libreswan/libreswan | https://github.com/libreswan/libreswan/commit/471a3e41a449d7c753bc4edbba4239501bb62ba8 | security: Fix for CVE-2020-1763
pluto will crash on a null pointer dereference when trying to log an error
for an IKEv1 packet containing bogus information and/or flags.
Signed-off-by: Paul Wouters <pwouters@redhat.com> | 1 | void process_packet_tail(struct msg_digest *md)
{
struct state *st = md->st;
enum state_kind from_state = md->v1_from_state;
const struct state_v1_microcode *smc = md->smc;
bool new_iv_set = md->new_iv_set;
bool self_delete = FALSE;
if (md->hdr.isa_flags & ISAKMP_FLAGS_v1_ENCRYPTION) {
endpoint_buf b;
dbg("r... | 63,827,285,309,811,410,000,000,000,000,000,000,000 | ikev1.c | 338,256,982,181,696,770,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-1763 | An out-of-bounds buffer read flaw was found in the pluto daemon of libreswan from versions 3.27 till 3.31 where, an unauthenticated attacker could use this flaw to crash libreswan by sending specially-crafted IKEv1 Informational Exchange packets. The daemon respawns after the crash. | https://nvd.nist.gov/vuln/detail/CVE-2020-1763 |
451,340 | libreswan | 471a3e41a449d7c753bc4edbba4239501bb62ba8 | https://github.com/libreswan/libreswan | https://github.com/libreswan/libreswan/commit/471a3e41a449d7c753bc4edbba4239501bb62ba8 | security: Fix for CVE-2020-1763
pluto will crash on a null pointer dereference when trying to log an error
for an IKEv1 packet containing bogus information and/or flags.
Signed-off-by: Paul Wouters <pwouters@redhat.com> | 0 | void process_packet_tail(struct msg_digest *md)
{
struct state *st = md->st;
enum state_kind from_state = md->v1_from_state;
const struct state_v1_microcode *smc = md->smc;
bool new_iv_set = md->new_iv_set;
bool self_delete = FALSE;
if (md->hdr.isa_flags & ISAKMP_FLAGS_v1_ENCRYPTION) {
endpoint_buf b;
dbg("r... | 26,997,564,680,850,255,000,000,000,000,000,000,000 | ikev1.c | 189,831,160,061,657,080,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-1763 | An out-of-bounds buffer read flaw was found in the pluto daemon of libreswan from versions 3.27 till 3.31 where, an unauthenticated attacker could use this flaw to crash libreswan by sending specially-crafted IKEv1 Informational Exchange packets. The daemon respawns after the crash. | https://nvd.nist.gov/vuln/detail/CVE-2020-1763 |
211,742 | ImageMagick | 784fcac688161aeaea221e00b706c88b08196945 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/784fcac688161aeaea221e00b706c88b08196945 | https://github.com/ImageMagick/ImageMagick/issues/555 | 1 | static Image *ReadWMFImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
double
bounding_height,
bounding_width,
image_height,
image_height_inch,
image_width,
image_width_inch,
resolution_y,
resolution_x,
units_per_inch;
float
wmf_width,
wmf_height;
Image
... | 283,729,192,542,878,400,000,000,000,000,000,000,000 | wmf.c | 98,501,591,122,886,250,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-12431 | In ImageMagick 7.0.6-1, a use-after-free vulnerability was found in the function ReadWMFImage in coders/wmf.c, which allows attackers to cause a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2017-12431 |
451,593 | ImageMagick | 784fcac688161aeaea221e00b706c88b08196945 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/784fcac688161aeaea221e00b706c88b08196945 | https://github.com/ImageMagick/ImageMagick/issues/555 | 0 | static Image *ReadWMFImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
double
bounding_height,
bounding_width,
image_height,
image_height_inch,
image_width,
image_width_inch,
resolution_y,
resolution_x,
units_per_inch;
float
wmf_width,
wmf_height;
Image
... | 146,326,967,484,147,030,000,000,000,000,000,000,000 | wmf.c | 251,013,373,940,853,630,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-12431 | In ImageMagick 7.0.6-1, a use-after-free vulnerability was found in the function ReadWMFImage in coders/wmf.c, which allows attackers to cause a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2017-12431 |
211,743 | bind9 | e4cccf9668c7adee4724a7649ec64685f82c8677 | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/-/commit/e4cccf9668c7adee4724a7649ec64685f82c8677 | Update-policy 'subdomain' was incorrectly treated as 'zonesub'
resulting in names outside the specified subdomain having the wrong
restrictions for the given key. | 1 | configure_zone_ssutable(const cfg_obj_t *zconfig, dns_zone_t *zone,
const char *zname)
{
const cfg_obj_t *updatepolicy = NULL;
const cfg_listelt_t *element, *element2;
dns_ssutable_t *table = NULL;
isc_mem_t *mctx = dns_zone_getmctx(zone);
bool autoddns = false;
isc_result_t result;
(void)cfg_map_get(zconfig... | 310,870,098,211,356,740,000,000,000,000,000,000,000 | zoneconf.c | 233,163,465,272,740,480,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2020-8624 | In BIND 9.9.12 -> 9.9.13, 9.10.7 -> 9.10.8, 9.11.3 -> 9.11.21, 9.12.1 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.12-S1 -> 9.9.13-S1, 9.11.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker who has been granted privileges to change a specific subset of the zone's content could abuse these uninten... | https://nvd.nist.gov/vuln/detail/CVE-2020-8624 |
451,594 | bind9 | e4cccf9668c7adee4724a7649ec64685f82c8677 | https://github.com/isc-projects/bind9 | https://gitlab.isc.org/isc-projects/bind9/-/commit/e4cccf9668c7adee4724a7649ec64685f82c8677 | Update-policy 'subdomain' was incorrectly treated as 'zonesub'
resulting in names outside the specified subdomain having the wrong
restrictions for the given key. | 0 | configure_zone_ssutable(const cfg_obj_t *zconfig, dns_zone_t *zone,
const char *zname)
{
const cfg_obj_t *updatepolicy = NULL;
const cfg_listelt_t *element, *element2;
dns_ssutable_t *table = NULL;
isc_mem_t *mctx = dns_zone_getmctx(zone);
bool autoddns = false;
isc_result_t result;
(void)cfg_map_get(zconfig... | 32,311,277,216,876,886,000,000,000,000,000,000,000 | zoneconf.c | 177,441,783,173,413,870,000,000,000,000,000,000,000 | [
"CWE-269"
] | CVE-2020-8624 | In BIND 9.9.12 -> 9.9.13, 9.10.7 -> 9.10.8, 9.11.3 -> 9.11.21, 9.12.1 -> 9.16.5, 9.17.0 -> 9.17.3, also affects 9.9.12-S1 -> 9.9.13-S1, 9.11.3-S1 -> 9.11.21-S1 of the BIND 9 Supported Preview Edition, An attacker who has been granted privileges to change a specific subset of the zone's content could abuse these uninten... | https://nvd.nist.gov/vuln/detail/CVE-2020-8624 |
211,748 | jasper | e6c8d5a838b49f94616be14753aa5c89d64605b5 | https://github.com/mdadams/jasper | https://github.com/jasper-software/jasper/commit/e6c8d5a838b49f94616be14753aa5c89d64605b5 | jpc_math: split jpc_firstone() in int/jpc_fix_t overloads
Fixes CVE-2018-9055 (denial of service via a reachable assertion due
to integer overflow).
Based on a patch from Fridrich Strba <fstrba@suse.com>. Instead of
switching to `int_fast32_t`, this patch splits jpc_firstone() into two
overloads, one for `int` and o... | 1 | int jpc_firstone(int x)
{
int n;
/* The argument must be nonnegative. */
assert(x >= 0);
n = -1;
while (x > 0) {
x >>= 1;
++n;
}
return n;
} | 329,744,770,639,869,430,000,000,000,000,000,000,000 | jpc_math.c | 38,023,672,292,525,494,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-9055 | JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_firstone in libjasper/jpc/jpc_math.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-9055 |
451,615 | jasper | e6c8d5a838b49f94616be14753aa5c89d64605b5 | https://github.com/mdadams/jasper | https://github.com/jasper-software/jasper/commit/e6c8d5a838b49f94616be14753aa5c89d64605b5 | jpc_math: split jpc_firstone() in int/jpc_fix_t overloads
Fixes CVE-2018-9055 (denial of service via a reachable assertion due
to integer overflow).
Based on a patch from Fridrich Strba <fstrba@suse.com>. Instead of
switching to `int_fast32_t`, this patch splits jpc_firstone() into two
overloads, one for `int` and o... | 0 | int jpc_int_firstone(int x)
{
int n;
/* The argument must be nonnegative. */
assert(x >= 0);
n = -1;
while (x > 0) {
x >>= 1;
++n;
}
return n;
} | 289,022,971,485,304,970,000,000,000,000,000,000,000 | jpc_math.c | 315,662,221,167,344,220,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2018-9055 | JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_firstone in libjasper/jpc/jpc_math.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-9055 |
211,757 | advancecomp | 7894a6e684ce68ddff9f4f4919ab8e3911ac8040 | https://github.com/amadvance/advancecomp | https://github.com/amadvance/advancecomp/commit/7894a6e684ce68ddff9f4f4919ab8e3911ac8040 | Fix a buffer overflow caused by invalid chunks | 1 | void png_print_chunk(unsigned type, unsigned char* data, unsigned size)
{
char tag[5];
unsigned i;
be_uint32_write(tag, type);
tag[4] = 0;
cout << tag << setw(8) << size;
switch (type) {
case ADV_MNG_CN_MHDR :
cout << " width:" << be_uint32_read(data+0) << " height:" << be_uint32_read(data+4) << " frequen... | 313,171,329,943,396,900,000,000,000,000,000,000,000 | pngex.cc | 299,908,436,731,755,440,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-9210 | In AdvanceCOMP 2.1, png_compress in pngex.cc in advpng has an integer overflow upon encountering an invalid PNG size, which results in an attempted memcpy to write into a buffer that is too small. (There is also a heap-based buffer over-read.) | https://nvd.nist.gov/vuln/detail/CVE-2019-9210 |
451,673 | advancecomp | 7894a6e684ce68ddff9f4f4919ab8e3911ac8040 | https://github.com/amadvance/advancecomp | https://github.com/amadvance/advancecomp/commit/7894a6e684ce68ddff9f4f4919ab8e3911ac8040 | Fix a buffer overflow caused by invalid chunks | 0 | void png_print_chunk(unsigned type, unsigned char* data, unsigned size)
{
char tag[5];
unsigned i;
be_uint32_write(tag, type);
tag[4] = 0;
cout << tag << setw(8) << size;
switch (type) {
case ADV_MNG_CN_MHDR :
if (size < 28) {
cout << " invalid chunk size";
break;
}
cout << " width:" << be_u... | 158,386,833,059,907,220,000,000,000,000,000,000,000 | pngex.cc | 64,116,049,195,592,860,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-9210 | In AdvanceCOMP 2.1, png_compress in pngex.cc in advpng has an integer overflow upon encountering an invalid PNG size, which results in an attempted memcpy to write into a buffer that is too small. (There is also a heap-based buffer over-read.) | https://nvd.nist.gov/vuln/detail/CVE-2019-9210 |
211,787 | bpf | 7d3baf0afa3aa9102d6a521a8e4c41888bb79882 | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=7d3baf0afa3aa9102d6a521a8e4c41888bb79882 | bpf: Fix kernel address leakage in atomic fetch
The change in commit 37086bfdc737 ("bpf: Propagate stack bounds to registers
in atomics w/ BPF_FETCH") around check_mem_access() handling is buggy since
this would allow for unprivileged users to leak kernel pointers. For example,
an atomic fetch/and with -1 on a stack d... | 1 | static int check_atomic(struct bpf_verifier_env *env, int insn_idx, struct bpf_insn *insn)
{
int load_reg;
int err;
switch (insn->imm) {
case BPF_ADD:
case BPF_ADD | BPF_FETCH:
case BPF_AND:
case BPF_AND | BPF_FETCH:
case BPF_OR:
case BPF_OR | BPF_FETCH:
case BPF_XOR:
case BPF_XOR | BPF_FETCH:
case BPF_XCH... | 145,330,698,009,460,200,000,000,000,000,000,000,000 | verifier.c | 236,987,114,413,270,300,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2022-0264 | A vulnerability was found in the Linux kernel's eBPF verifier when handling internal data structures. Internal memory locations could be returned to userspace. A local attacker with the permissions to insert eBPF code to the kernel can use this to leak internal kernel memory details defeating some of the exploit mitiga... | https://nvd.nist.gov/vuln/detail/CVE-2022-0264 |
451,891 | bpf | 7d3baf0afa3aa9102d6a521a8e4c41888bb79882 | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=7d3baf0afa3aa9102d6a521a8e4c41888bb79882 | bpf: Fix kernel address leakage in atomic fetch
The change in commit 37086bfdc737 ("bpf: Propagate stack bounds to registers
in atomics w/ BPF_FETCH") around check_mem_access() handling is buggy since
this would allow for unprivileged users to leak kernel pointers. For example,
an atomic fetch/and with -1 on a stack d... | 0 | static int check_atomic(struct bpf_verifier_env *env, int insn_idx, struct bpf_insn *insn)
{
int load_reg;
int err;
switch (insn->imm) {
case BPF_ADD:
case BPF_ADD | BPF_FETCH:
case BPF_AND:
case BPF_AND | BPF_FETCH:
case BPF_OR:
case BPF_OR | BPF_FETCH:
case BPF_XOR:
case BPF_XOR | BPF_FETCH:
case BPF_XCH... | 266,055,497,991,564,800,000,000,000,000,000,000,000 | verifier.c | 255,444,479,356,829,200,000,000,000,000,000,000,000 | [
"CWE-755"
] | CVE-2022-0264 | A vulnerability was found in the Linux kernel's eBPF verifier when handling internal data structures. Internal memory locations could be returned to userspace. A local attacker with the permissions to insert eBPF code to the kernel can use this to leak internal kernel memory details defeating some of the exploit mitiga... | https://nvd.nist.gov/vuln/detail/CVE-2022-0264 |
211,796 | evolution-data-server | 6672b8236139bd6ef41ecb915f4c72e2a052dba5 | https://git.gnome.org/browse/evolution-data-server | https://gitlab.gnome.org/GNOME/evolution-data-server/commit/6672b8236139bd6ef41ecb915f4c72e2a052dba5 | Let child source with 'none' authentication method use collection source authentication
That might be the same as having set NULL authentication method.
Related to https://gitlab.gnome.org/GNOME/evolution-ews/issues/27 | 1 | e_util_can_use_collection_as_credential_source (ESource *collection_source,
ESource *child_source)
{
gboolean can_use_collection = FALSE;
if (collection_source)
g_return_val_if_fail (E_IS_SOURCE (collection_source), FALSE);
g_return_val_if_fail (E_IS_SOURCE (child_source), FALSE);
if (collection_source &&... | 106,276,112,764,024,500,000,000,000,000,000,000,000 | e-data-server-util.c | 77,613,276,258,081,710,000,000,000,000,000,000,000 | [
"CWE-295"
] | CVE-2019-3890 | It was discovered evolution-ews before 3.31.3 does not check the validity of SSL certificates. An attacker could abuse this flaw to get confidential information by tricking the user into connecting to a fake server without the user noticing the difference. | https://nvd.nist.gov/vuln/detail/CVE-2019-3890 |
452,038 | evolution-data-server | 6672b8236139bd6ef41ecb915f4c72e2a052dba5 | https://git.gnome.org/browse/evolution-data-server | https://gitlab.gnome.org/GNOME/evolution-data-server/commit/6672b8236139bd6ef41ecb915f4c72e2a052dba5 | Let child source with 'none' authentication method use collection source authentication
That might be the same as having set NULL authentication method.
Related to https://gitlab.gnome.org/GNOME/evolution-ews/issues/27 | 0 | e_util_can_use_collection_as_credential_source (ESource *collection_source,
ESource *child_source)
{
gboolean can_use_collection = FALSE;
if (collection_source)
g_return_val_if_fail (E_IS_SOURCE (collection_source), FALSE);
g_return_val_if_fail (E_IS_SOURCE (child_source), FALSE);
if (collection_source &&... | 4,183,317,600,470,360,000,000,000,000,000,000,000 | e-data-server-util.c | 128,781,271,160,396,590,000,000,000,000,000,000,000 | [
"CWE-295"
] | CVE-2019-3890 | It was discovered evolution-ews before 3.31.3 does not check the validity of SSL certificates. An attacker could abuse this flaw to get confidential information by tricking the user into connecting to a fake server without the user noticing the difference. | https://nvd.nist.gov/vuln/detail/CVE-2019-3890 |
211,798 | php-src | 69155120e68d2e614d5c300974a1a5610cfa2e8b | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=69155120e68d2e614d5c300974a1a5610cfa2e8b | Fix #79371: mb_strtolower (UTF-32LE): stack-buffer-overflow
We make sure that negative values are properly compared. | 1 | static int convert_case_filter(int c, void *void_data)
{
struct convert_case_data *data = (struct convert_case_data *) void_data;
unsigned out[3];
unsigned len, i;
/* Handle invalid characters early, as we assign special meaning to
* codepoints above 0xffffff. */
if (UNEXPECTED(c > 0xffffff)) {
(*data->next_f... | 67,331,134,053,111,670,000,000,000,000,000,000,000 | php_unicode.c | 183,977,171,609,088,720,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-7065 | In PHP versions 7.3.x below 7.3.16 and 7.4.x below 7.4.4, while using mb_strtolower() function with UTF-32LE encoding, certain invalid strings could cause PHP to overwrite stack-allocated buffer. This could lead to memory corruption, crashes and potentially code execution. | https://nvd.nist.gov/vuln/detail/CVE-2020-7065 |
452,110 | php-src | 69155120e68d2e614d5c300974a1a5610cfa2e8b | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=69155120e68d2e614d5c300974a1a5610cfa2e8b | Fix #79371: mb_strtolower (UTF-32LE): stack-buffer-overflow
We make sure that negative values are properly compared. | 0 | static int convert_case_filter(int c, void *void_data)
{
struct convert_case_data *data = (struct convert_case_data *) void_data;
unsigned out[3];
unsigned len, i;
/* Handle invalid characters early, as we assign special meaning to
* codepoints above 0xffffff. */
if (UNEXPECTED((unsigned) c > 0xffffff)) {
(*d... | 328,299,474,463,433,170,000,000,000,000,000,000,000 | php_unicode.c | 201,832,250,475,376,200,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-7065 | In PHP versions 7.3.x below 7.3.16 and 7.4.x below 7.4.4, while using mb_strtolower() function with UTF-32LE encoding, certain invalid strings could cause PHP to overwrite stack-allocated buffer. This could lead to memory corruption, crashes and potentially code execution. | https://nvd.nist.gov/vuln/detail/CVE-2020-7065 |
211,800 | openldap | 9d0e8485f3113505743baabf1167e01e4558ccf5 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/9d0e8485f3113505743baabf1167e01e4558ccf5 | ITS#9428 fix cancel exop | 1 | int cancel_extop( Operation *op, SlapReply *rs )
{
Operation *o;
int rc;
int opid;
BerElementBuffer berbuf;
BerElement *ber = (BerElement *)&berbuf;
assert( ber_bvcmp( &slap_EXOP_CANCEL, &op->ore_reqoid ) == 0 );
if ( op->ore_reqdata == NULL ) {
rs->sr_text = "no message ID supplied";
return LDAP_PROTOCOL_... | 260,013,810,663,979,250,000,000,000,000,000,000,000 | cancel.c | 330,842,096,246,867,420,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2020-36227 | A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-36227 |
452,125 | openldap | 9d0e8485f3113505743baabf1167e01e4558ccf5 | https://github.com/openldap/openldap | https://git.openldap.org/openldap/openldap/-/commit/9d0e8485f3113505743baabf1167e01e4558ccf5 | ITS#9428 fix cancel exop | 0 | int cancel_extop( Operation *op, SlapReply *rs )
{
Operation *o;
int rc;
int opid;
BerElementBuffer berbuf;
BerElement *ber = (BerElement *)&berbuf;
assert( ber_bvcmp( &slap_EXOP_CANCEL, &op->ore_reqoid ) == 0 );
if ( op->ore_reqdata == NULL ) {
rs->sr_text = "no message ID supplied";
return LDAP_PROTOCOL_... | 258,059,311,193,965,130,000,000,000,000,000,000,000 | cancel.c | 315,770,252,955,407,400,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2020-36227 | A flaw was discovered in OpenLDAP before 2.4.57 leading to an infinite loop in slapd with the cancel_extop Cancel operation, resulting in denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2020-36227 |
211,801 | openexr | b0c63c0b96eb9b0d3998f603e12f9f414fb0d44a | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/b0c63c0b96eb9b0d3998f603e12f9f414fb0d44a | double-check unpackedBuffer created in DWA uncompress
Signed-off-by: Peter Hillman <peterh@wetafx.co.nz> | 1 | DwaCompressor::uncompress
(const char *inPtr,
int inSize,
IMATH_NAMESPACE::Box2i range,
const char *&outPtr)
{
int minX = range.min.x;
int maxX = std::min (range.max.x, _max[0]);
int minY = range.min.y;
int maxY = std::min (range.max.y, _max[1]);
Int64 iSize = static_cast<Int64>(... | 297,699,748,995,215,460,000,000,000,000,000,000,000 | ImfDwaCompressor.cpp | 75,892,435,005,838,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-20296 | A flaw was found in OpenEXR in versions before 3.0.0-beta. A crafted input file supplied by an attacker, that is processed by the Dwa decompression functionality of OpenEXR's IlmImf library, could cause a NULL pointer dereference. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20296 |
452,126 | openexr | b0c63c0b96eb9b0d3998f603e12f9f414fb0d44a | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/b0c63c0b96eb9b0d3998f603e12f9f414fb0d44a | double-check unpackedBuffer created in DWA uncompress
Signed-off-by: Peter Hillman <peterh@wetafx.co.nz> | 0 | DwaCompressor::uncompress
(const char *inPtr,
int inSize,
IMATH_NAMESPACE::Box2i range,
const char *&outPtr)
{
int minX = range.min.x;
int maxX = std::min (range.max.x, _max[0]);
int minY = range.min.y;
int maxY = std::min (range.max.y, _max[1]);
Int64 iSize = static_cast<Int64>(... | 56,848,410,176,015,595,000,000,000,000,000,000,000 | ImfDwaCompressor.cpp | 207,441,190,425,488,400,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-20296 | A flaw was found in OpenEXR in versions before 3.0.0-beta. A crafted input file supplied by an attacker, that is processed by the Dwa decompression functionality of OpenEXR's IlmImf library, could cause a NULL pointer dereference. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20296 |
211,802 | linux | b5a8ffcae4103a9d823ea3aa3a761f65779fbe2a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b5a8ffcae4103a9d823ea3aa3a761f65779fbe2a | wil6210: missing length check in wmi_set_ie
Add a length check in wmi_set_ie to detect unsigned integer
overflow.
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> | 1 | int wmi_set_ie(struct wil6210_priv *wil, u8 type, u16 ie_len, const void *ie)
{
static const char *const names[] = {
[WMI_FRAME_BEACON] = "BEACON",
[WMI_FRAME_PROBE_REQ] = "PROBE_REQ",
[WMI_FRAME_PROBE_RESP] = "WMI_FRAME_PROBE_RESP",
[WMI_FRAME_ASSOC_REQ] = "WMI_FRAME_ASSOC_REQ",
[WMI_FRAME_ASSOC_RESP] = "WM... | 337,396,821,340,592,850,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-5848 | In the function wmi_set_ie(), the length validation code does not handle unsigned integer overflow properly. As a result, a large value of the 'ie_len' argument can cause a buffer overflow in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel. | https://nvd.nist.gov/vuln/detail/CVE-2018-5848 |
452,177 | linux | b5a8ffcae4103a9d823ea3aa3a761f65779fbe2a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b5a8ffcae4103a9d823ea3aa3a761f65779fbe2a | wil6210: missing length check in wmi_set_ie
Add a length check in wmi_set_ie to detect unsigned integer
overflow.
Signed-off-by: Lior David <qca_liord@qca.qualcomm.com>
Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> | 0 | int wmi_set_ie(struct wil6210_priv *wil, u8 type, u16 ie_len, const void *ie)
{
static const char *const names[] = {
[WMI_FRAME_BEACON] = "BEACON",
[WMI_FRAME_PROBE_REQ] = "PROBE_REQ",
[WMI_FRAME_PROBE_RESP] = "WMI_FRAME_PROBE_RESP",
[WMI_FRAME_ASSOC_REQ] = "WMI_FRAME_ASSOC_REQ",
[WMI_FRAME_ASSOC_RESP] = "WM... | 89,989,040,149,802,810,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2018-5848 | In the function wmi_set_ie(), the length validation code does not handle unsigned integer overflow properly. As a result, a large value of the 'ie_len' argument can cause a buffer overflow in all Android releases from CAF (Android for MSM, Firefox OS for MSM, QRD Android) using the Linux Kernel. | https://nvd.nist.gov/vuln/detail/CVE-2018-5848 |
211,822 | ModSecurity | f8d441cd25172fdfe5b613442fedfc0da3cc333d | https://github.com/SpiderLabs/ModSecurity | https://github.com/SpiderLabs/ModSecurity/commit/f8d441cd25172fdfe5b613442fedfc0da3cc333d | Fix Chunked string case sensitive issue - CVE-2013-5705 | 1 | apr_status_t modsecurity_tx_init(modsec_rec *msr) {
const char *s = NULL;
const apr_array_header_t *arr;
char *semicolon = NULL;
char *comma = NULL;
apr_table_entry_t *te;
int i;
/* Register TX cleanup */
apr_pool_cleanup_register(msr->mp, msr, modsecurity_tx_cleanup, apr_pool_cleanup_n... | 259,126,583,575,738,230,000,000,000,000,000,000,000 | modsecurity.c | 226,644,691,712,120,750,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-5705 | apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header. | https://nvd.nist.gov/vuln/detail/CVE-2013-5705 |
452,282 | ModSecurity | f8d441cd25172fdfe5b613442fedfc0da3cc333d | https://github.com/SpiderLabs/ModSecurity | https://github.com/SpiderLabs/ModSecurity/commit/f8d441cd25172fdfe5b613442fedfc0da3cc333d | Fix Chunked string case sensitive issue - CVE-2013-5705 | 0 | apr_status_t modsecurity_tx_init(modsec_rec *msr) {
const char *s = NULL;
const apr_array_header_t *arr;
char *semicolon = NULL;
char *comma = NULL;
apr_table_entry_t *te;
int i;
/* Register TX cleanup */
apr_pool_cleanup_register(msr->mp, msr, modsecurity_tx_cleanup, apr_pool_cleanup_n... | 129,253,822,198,087,480,000,000,000,000,000,000,000 | modsecurity.c | 315,770,727,899,994,600,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-5705 | apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header. | https://nvd.nist.gov/vuln/detail/CVE-2013-5705 |
211,836 | gnutls | 5164d5a1d57cd0372a5dd074382ca960ca18b27d | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/5164d5a1d57cd0372a5dd074382ca960ca18b27d | re-applied sanity check patch | 1 | _gnutls_ciphertext2compressed (gnutls_session_t session,
opaque * compress_data,
int compress_size,
gnutls_datum_t ciphertext, uint8_t type,
record_parameters_st * params)
{
uint8_t MAC[MAX_HASH... | 235,105,230,697,710,500,000,000,000,000,000,000,000 | gnutls_cipher.c | 338,402,166,891,933,630,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-2116 | The _gnutls_ciphertext2compressed function in lib/gnutls_cipher.c in GnuTLS 2.12.23 allows remote attackers to cause a denial of service (buffer over-read and crash) via a crafted padding length. NOTE: this might be due to an incorrect fix for CVE-2013-0169. | https://nvd.nist.gov/vuln/detail/CVE-2013-2116 |
452,354 | gnutls | 5164d5a1d57cd0372a5dd074382ca960ca18b27d | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/5164d5a1d57cd0372a5dd074382ca960ca18b27d | re-applied sanity check patch | 0 | _gnutls_ciphertext2compressed (gnutls_session_t session,
opaque * compress_data,
int compress_size,
gnutls_datum_t ciphertext, uint8_t type,
record_parameters_st * params)
{
uint8_t MAC[MAX_HASH... | 60,511,410,850,999,470,000,000,000,000,000,000,000 | gnutls_cipher.c | 127,931,477,813,659,430,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-2116 | The _gnutls_ciphertext2compressed function in lib/gnutls_cipher.c in GnuTLS 2.12.23 allows remote attackers to cause a denial of service (buffer over-read and crash) via a crafted padding length. NOTE: this might be due to an incorrect fix for CVE-2013-0169. | https://nvd.nist.gov/vuln/detail/CVE-2013-2116 |
211,841 | Sigil | 04e2f280cc4a0766bedcc7b9eb56449ceecc2ad4 | https://github.com/Sigil-Ebook/Sigil | https://github.com/Sigil-Ebook/Sigil/commit/04e2f280cc4a0766bedcc7b9eb56449ceecc2ad4 | further harden against malicious epubs and produce error message | 1 | void ImportEPUB::ExtractContainer()
{
int res = 0;
if (!cp437) {
cp437 = new QCodePage437Codec();
}
#ifdef Q_OS_WIN32
zlib_filefunc64_def ffunc;
fill_win32_filefunc64W(&ffunc);
unzFile zfile = unzOpen2_64(Utility::QStringToStdWString(QDir::toNativeSeparators(m_FullFilePath)).c_str(), &ff... | 283,084,649,470,288,360,000,000,000,000,000,000,000 | ImportEPUB.cpp | 243,627,040,167,276,200,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2019-14452 | Sigil before 0.9.16 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in a ZIP archive entry that is mishandled during extraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-14452 |
452,363 | Sigil | 04e2f280cc4a0766bedcc7b9eb56449ceecc2ad4 | https://github.com/Sigil-Ebook/Sigil | https://github.com/Sigil-Ebook/Sigil/commit/04e2f280cc4a0766bedcc7b9eb56449ceecc2ad4 | further harden against malicious epubs and produce error message | 0 | void ImportEPUB::ExtractContainer()
{
int res = 0;
if (!cp437) {
cp437 = new QCodePage437Codec();
}
#ifdef Q_OS_WIN32
zlib_filefunc64_def ffunc;
fill_win32_filefunc64W(&ffunc);
unzFile zfile = unzOpen2_64(Utility::QStringToStdWString(QDir::toNativeSeparators(m_FullFilePath)).c_str(), &ff... | 275,392,502,660,148,760,000,000,000,000,000,000,000 | ImportEPUB.cpp | 15,516,234,330,483,436,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2019-14452 | Sigil before 0.9.16 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in a ZIP archive entry that is mishandled during extraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-14452 |
211,851 | mutt | 3287534daa3beac68e2e83ca4b4fe8a3148ff870 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/commit/3287534daa3beac68e2e83ca4b4fe8a3148ff870 | Don't overflow tmp in msg_parse_fetch.
Ensure INTERNALDATE and RFC822.SIZE field sizes fit temp buffer.
Thanks to Jeriko One for the bug report and patch, which this patch is
based upon. | 1 | static int msg_parse_fetch (IMAP_HEADER *h, char *s)
{
char tmp[SHORT_STRING];
char *ptmp;
if (!s)
return -1;
while (*s)
{
SKIPWS (s);
if (ascii_strncasecmp ("FLAGS", s, 5) == 0)
{
if ((s = msg_parse_flags (h, s)) == NULL)
return -1;
}
else if (ascii_strncasecmp ("UID"... | 186,983,865,612,921,260,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-14350 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field. | https://nvd.nist.gov/vuln/detail/CVE-2018-14350 |
452,602 | mutt | 3287534daa3beac68e2e83ca4b4fe8a3148ff870 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/commit/3287534daa3beac68e2e83ca4b4fe8a3148ff870 | Don't overflow tmp in msg_parse_fetch.
Ensure INTERNALDATE and RFC822.SIZE field sizes fit temp buffer.
Thanks to Jeriko One for the bug report and patch, which this patch is
based upon. | 0 | static int msg_parse_fetch (IMAP_HEADER *h, char *s)
{
char tmp[SHORT_STRING];
char *ptmp;
size_t dlen;
if (!s)
return -1;
while (*s)
{
SKIPWS (s);
if (ascii_strncasecmp ("FLAGS", s, 5) == 0)
{
if ((s = msg_parse_flags (h, s)) == NULL)
return -1;
}
else if (ascii_str... | 197,471,801,062,440,540,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-14350 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/message.c has a stack-based buffer overflow for a FETCH response with a long INTERNALDATE field. | https://nvd.nist.gov/vuln/detail/CVE-2018-14350 |
211,856 | linux | 9f46c187e2e680ecd9de7983e4d081c3391acc76 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9f46c187e2e680ecd9de7983e4d081c3391acc76 | KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID
With shadow paging enabled, the INVPCID instruction results in a call
to kvm_mmu_invpcid_gva. If INVPCID is executed with CR0.PG=0, the
invlpg callback is not set and the result is a NULL pointer dereference.
Fix it trivially by checking for mmu->invlpg befo... | 1 | void kvm_mmu_invpcid_gva(struct kvm_vcpu *vcpu, gva_t gva, unsigned long pcid)
{
struct kvm_mmu *mmu = vcpu->arch.mmu;
bool tlb_flush = false;
uint i;
if (pcid == kvm_get_active_pcid(vcpu)) {
mmu->invlpg(vcpu, gva, mmu->root.hpa);
tlb_flush = true;
}
for (i = 0; i < KVM_MMU_NUM_PREV_ROOTS; i++) {
if (VALI... | 335,809,160,847,580,550,000,000,000,000,000,000,000 | mmu.c | 11,215,951,012,969,957,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-1789 | With shadow paging enabled, the INVPCID instruction results in a call to kvm_mmu_invpcid_gva. If INVPCID is executed with CR0.PG=0, the invlpg callback is not set and the result is a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2022-1789 |
452,691 | linux | 9f46c187e2e680ecd9de7983e4d081c3391acc76 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9f46c187e2e680ecd9de7983e4d081c3391acc76 | KVM: x86/mmu: fix NULL pointer dereference on guest INVPCID
With shadow paging enabled, the INVPCID instruction results in a call
to kvm_mmu_invpcid_gva. If INVPCID is executed with CR0.PG=0, the
invlpg callback is not set and the result is a NULL pointer dereference.
Fix it trivially by checking for mmu->invlpg befo... | 0 | void kvm_mmu_invpcid_gva(struct kvm_vcpu *vcpu, gva_t gva, unsigned long pcid)
{
struct kvm_mmu *mmu = vcpu->arch.mmu;
bool tlb_flush = false;
uint i;
if (pcid == kvm_get_active_pcid(vcpu)) {
if (mmu->invlpg)
mmu->invlpg(vcpu, gva, mmu->root.hpa);
tlb_flush = true;
}
for (i = 0; i < KVM_MMU_NUM_PREV_ROOT... | 316,978,811,727,031,400,000,000,000,000,000,000,000 | mmu.c | 71,266,076,254,608,070,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2022-1789 | With shadow paging enabled, the INVPCID instruction results in a call to kvm_mmu_invpcid_gva. If INVPCID is executed with CR0.PG=0, the invlpg callback is not set and the result is a NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2022-1789 |
211,896 | teeworlds | a766cb44bcffcdb0b88e776d01c5ee1323d44f85 | https://github.com/teeworlds/teeworlds | https://github.com/teeworlds/teeworlds/commit/a766cb44bcffcdb0b88e776d01c5ee1323d44f85 | fixed a server crash | 1 | void CServer::ProcessClientPacket(CNetChunk *pPacket)
{
int ClientID = pPacket->m_ClientID;
CUnpacker Unpacker;
Unpacker.Reset(pPacket->m_pData, pPacket->m_DataSize);
// unpack msgid and system flag
int Msg = Unpacker.GetInt();
int Sys = Msg&1;
Msg >>= 1;
if(Unpacker.Error())
return;
if(Sys)
{
// syste... | 238,431,673,763,313,570,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-9351 | engine/server/server.cpp in Teeworlds 0.6.x before 0.6.3 allows remote attackers to read memory and cause a denial of service (crash) via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2014-9351 |
453,163 | teeworlds | a766cb44bcffcdb0b88e776d01c5ee1323d44f85 | https://github.com/teeworlds/teeworlds | https://github.com/teeworlds/teeworlds/commit/a766cb44bcffcdb0b88e776d01c5ee1323d44f85 | fixed a server crash | 0 | void CServer::ProcessClientPacket(CNetChunk *pPacket)
{
int ClientID = pPacket->m_ClientID;
CUnpacker Unpacker;
Unpacker.Reset(pPacket->m_pData, pPacket->m_DataSize);
// unpack msgid and system flag
int Msg = Unpacker.GetInt();
int Sys = Msg&1;
Msg >>= 1;
if(Unpacker.Error())
return;
if(Sys)
{
// syste... | 230,000,324,170,952,800,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2014-9351 | engine/server/server.cpp in Teeworlds 0.6.x before 0.6.3 allows remote attackers to read memory and cause a denial of service (crash) via unspecified vectors. | https://nvd.nist.gov/vuln/detail/CVE-2014-9351 |
211,897 | httpd | fa7b2a5250e54363b3a6c8ac3aaa7de4e8da9b2e | https://github.com/apache/httpd | https://github.com/apache/httpd/commit/fa7b2a5250e54363b3a6c8ac3aaa7de4e8da9b2e | Merge r1878092 from trunk:
Fix a NULL pointer dereference
* server/scoreboard.c (ap_increment_counts): In certain cases like certain
invalid requests r->method might be NULL here. r->method_number defaults
to M_GET and hence is M_GET in these cases.
Submitted by: rpluem
Reviewed by: covener, ylavic, jfclere
gi... | 1 | AP_DECLARE(void) ap_increment_counts(ap_sb_handle_t *sb, request_rec *r)
{
worker_score *ws;
apr_off_t bytes;
if (!sb)
return;
ws = &ap_scoreboard_image->servers[sb->child_num][sb->thread_num];
if (pfn_ap_logio_get_last_bytes != NULL) {
bytes = pfn_ap_logio_get_last_bytes(r->connec... | 228,403,222,960,086,500,000,000,000,000,000,000,000 | scoreboard.c | 208,033,638,561,255,940,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-34798 | Malformed requests may cause the server to dereference a NULL pointer. This issue affects Apache HTTP Server 2.4.48 and earlier. | https://nvd.nist.gov/vuln/detail/CVE-2021-34798 |
453,173 | httpd | fa7b2a5250e54363b3a6c8ac3aaa7de4e8da9b2e | https://github.com/apache/httpd | https://github.com/apache/httpd/commit/fa7b2a5250e54363b3a6c8ac3aaa7de4e8da9b2e | Merge r1878092 from trunk:
Fix a NULL pointer dereference
* server/scoreboard.c (ap_increment_counts): In certain cases like certain
invalid requests r->method might be NULL here. r->method_number defaults
to M_GET and hence is M_GET in these cases.
Submitted by: rpluem
Reviewed by: covener, ylavic, jfclere
gi... | 0 | AP_DECLARE(void) ap_increment_counts(ap_sb_handle_t *sb, request_rec *r)
{
worker_score *ws;
apr_off_t bytes;
if (!sb)
return;
ws = &ap_scoreboard_image->servers[sb->child_num][sb->thread_num];
if (pfn_ap_logio_get_last_bytes != NULL) {
bytes = pfn_ap_logio_get_last_bytes(r->connec... | 228,144,888,832,807,550,000,000,000,000,000,000,000 | scoreboard.c | 155,871,899,649,399,360,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2021-34798 | Malformed requests may cause the server to dereference a NULL pointer. This issue affects Apache HTTP Server 2.4.48 and earlier. | https://nvd.nist.gov/vuln/detail/CVE-2021-34798 |
211,916 | libsass | 210fdff7a65370c2ae24e022a2b35da8c423cc5f | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/210fdff7a65370c2ae24e022a2b35da8c423cc5f | Remove legacy workaround for parsing modulo operator
Fixes #2659 | 1 | Expression_Obj Parser::parse_value()
{
lex< css_comments >(false);
if (lex< ampersand >())
{
if (match< ampersand >()) {
warning("In Sass, \"&&\" means two copies of the parent selector. You probably want to use \"and\" instead.", pstate);
}
return SASS_MEMORY_NEW(Parent_Select... | 39,812,967,477,514,900,000,000,000,000,000,000,000 | parser.cpp | 279,889,382,900,828,750,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2018-19837 | In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2018-19837 |
453,266 | libsass | 210fdff7a65370c2ae24e022a2b35da8c423cc5f | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/210fdff7a65370c2ae24e022a2b35da8c423cc5f | Remove legacy workaround for parsing modulo operator
Fixes #2659 | 0 | Expression_Obj Parser::parse_value()
{
lex< css_comments >(false);
if (lex< ampersand >())
{
if (match< ampersand >()) {
warning("In Sass, \"&&\" means two copies of the parent selector. You probably want to use \"and\" instead.", pstate);
}
return SASS_MEMORY_NEW(Parent_Select... | 98,919,753,463,118,620,000,000,000,000,000,000,000 | parser.cpp | 105,861,640,874,557,320,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2018-19837 | In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp. | https://nvd.nist.gov/vuln/detail/CVE-2018-19837 |
211,917 | net-next | bf39b4247b8799935ea91d90db250ab608a58e50 | http://git.kernel.org/?p=linux/kernel/git/davem/net-next | http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/net/rds/iw.c?id=bf39b4247b8799935ea91d90db250ab608a58e50 | rds: prevent dereference of a NULL device in rds_iw_laddr_check
Binding might result in a NULL device which is later dereferenced
without checking.
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | static int rds_iw_laddr_check(__be32 addr)
{
int ret;
struct rdma_cm_id *cm_id;
struct sockaddr_in sin;
/* Create a CMA ID and try to bind it. This catches both
* IB and iWARP capable NICs.
*/
cm_id = rdma_create_id(NULL, NULL, RDMA_PS_TCP, IB_QPT_RC);
if (IS_ERR(cm_id))
return PTR_ERR(cm_id);
memset(&si... | 318,040,449,322,178,670,000,000,000,000,000,000,000 | iw.c | 77,402,257,296,484,250,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2014-2678 | The rds_iw_laddr_check function in net/rds/iw.c in the Linux kernel through 3.14 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a bind system call for an RDS socket on a system that lacks RDS transports. | https://nvd.nist.gov/vuln/detail/CVE-2014-2678 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.