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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
409,093 | LibRaw | 20ad21c0d87ca80217aee47533d91e633ce1864d | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/20ad21c0d87ca80217aee47533d91e633ce1864d | Thumbnail size range check | 0 | void LibRaw::kodak_thumb_loader()
{
INT64 est_datasize =
T.theight * T.twidth / 3; // is 0.3 bytes per pixel good estimate?
if (ID.toffset < 0)
throw LIBRAW_EXCEPTION_IO_CORRUPT;
if (ID.toffset + est_datasize > ID.input->size() + THUMB_READ_BEYOND)
throw LIBRAW_EXCEPTION_IO_EOF;
if(INT64(T.theig... | 184,056,746,953,962,300,000,000,000,000,000,000,000 | thumb_utils.cpp | 9,869,676,747,915,515,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-15503 | LibRaw before 0.20-RC1 lacks a thumbnail size range check. This affects decoders/unpack_thumb.cpp, postprocessing/mem_image.cpp, and utils/thumb_utils.cpp. For example, malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs without validating T.tlength. | https://nvd.nist.gov/vuln/detail/CVE-2020-15503 |
208,377 | LibRaw | 20ad21c0d87ca80217aee47533d91e633ce1864d | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/20ad21c0d87ca80217aee47533d91e633ce1864d | Thumbnail size range check | 1 | int LibRaw::unpack_thumb(void)
{
CHECK_ORDER_LOW(LIBRAW_PROGRESS_IDENTIFY);
CHECK_ORDER_BIT(LIBRAW_PROGRESS_THUMB_LOAD);
try
{
if (!libraw_internal_data.internal_data.input)
return LIBRAW_INPUT_CLOSED;
int t_colors = libraw_internal_data.unpacker_data.thumb_misc >> 5 & 7;
int t_bytesps = (li... | 252,313,122,752,249,720,000,000,000,000,000,000,000 | unpack_thumb.cpp | 32,663,867,400,658,210,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-15503 | LibRaw before 0.20-RC1 lacks a thumbnail size range check. This affects decoders/unpack_thumb.cpp, postprocessing/mem_image.cpp, and utils/thumb_utils.cpp. For example, malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs without validating T.tlength. | https://nvd.nist.gov/vuln/detail/CVE-2020-15503 |
409,094 | LibRaw | 20ad21c0d87ca80217aee47533d91e633ce1864d | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/20ad21c0d87ca80217aee47533d91e633ce1864d | Thumbnail size range check | 0 | int LibRaw::unpack_thumb(void)
{
CHECK_ORDER_LOW(LIBRAW_PROGRESS_IDENTIFY);
CHECK_ORDER_BIT(LIBRAW_PROGRESS_THUMB_LOAD);
#define THUMB_SIZE_CHECKT(A) \
do { \
if (INT64(A) > 1024ULL * 1024ULL * LIBRAW_MAX_THUMBNAIL_MB) throw LIBRAW_EXCEPTION_IO_CORRUPT; \
if (INT64(A) > 0 && INT64(A) < 64ULL) thr... | 28,300,783,953,354,540,000,000,000,000,000,000,000 | unpack_thumb.cpp | 136,803,322,702,681,940,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2020-15503 | LibRaw before 0.20-RC1 lacks a thumbnail size range check. This affects decoders/unpack_thumb.cpp, postprocessing/mem_image.cpp, and utils/thumb_utils.cpp. For example, malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs without validating T.tlength. | https://nvd.nist.gov/vuln/detail/CVE-2020-15503 |
208,378 | percona-xtradb-cluster | 8a338477c9184dd0e03a5c661e9c3a79456de8a4 | https://github.com/percona/percona-xtradb-cluster | https://github.com/percona/percona-xtradb-cluster/commit/8a338477c9184dd0e03a5c661e9c3a79456de8a4 | PXC-3392: Donor uses invalid SST methods | 1 | int wsrep_sst_donate(const std::string &msg, const wsrep::gtid ¤t_gtid,
const bool bypass) {
/* This will be reset when sync callback is called.
* Should we set wsrep_ready to false here too? */
local_status.set(wsrep::server_state::s_donor);
const char *method = msg.data();
size_... | 212,005,400,467,373,520,000,000,000,000,000,000,000 | wsrep_sst.cc | 44,268,913,517,546,990,000,000,000,000,000,000,000 | [
"CWE-77"
] | CVE-2020-15180 | A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` allows for command injection that can be exploited by a remote attacker to execute arbitrary commands on galera cluster nodes. This threatens the system's confidentiality, integrity, and availability. This flaw af... | https://nvd.nist.gov/vuln/detail/CVE-2020-15180 |
409,112 | percona-xtradb-cluster | 8a338477c9184dd0e03a5c661e9c3a79456de8a4 | https://github.com/percona/percona-xtradb-cluster | https://github.com/percona/percona-xtradb-cluster/commit/8a338477c9184dd0e03a5c661e9c3a79456de8a4 | PXC-3392: Donor uses invalid SST methods | 0 | int wsrep_sst_donate(const std::string &msg, const wsrep::gtid ¤t_gtid,
const bool bypass) {
/* This will be reset when sync callback is called.
* Should we set wsrep_ready to false here too? */
local_status.set(wsrep::server_state::s_donor);
if (!is_sst_request_valid(msg)) {
st... | 168,806,957,052,916,130,000,000,000,000,000,000,000 | wsrep_sst.cc | 7,489,626,014,399,923,000,000,000,000,000,000,000 | [
"CWE-77"
] | CVE-2020-15180 | A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` allows for command injection that can be exploited by a remote attacker to execute arbitrary commands on galera cluster nodes. This threatens the system's confidentiality, integrity, and availability. This flaw af... | https://nvd.nist.gov/vuln/detail/CVE-2020-15180 |
208,383 | exiv2 | 1647908e00a4df7246d76678e59587e62c690dcd | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/1647908e00a4df7246d76678e59587e62c690dcd | fix for crash in bigtiff (issue #208) | 1 | Header readHeader(BasicIo& io)
{
byte header[2];
io.read(header, 2);
ByteOrder byteOrder = invalidByteOrder;
if (header[0] == 'I' && header[1] == 'I')
byteOrder = littleEndian;
else if (header[0] == 'M' && header[1] == 'M')
... | 76,197,992,210,680,550,000,000,000,000,000,000,000 | bigtiffimage.cpp | 267,456,555,434,555,500,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2017-17722 | In Exiv2 0.26, there is a reachable assertion in the readHeader function in bigtiffimage.cpp, which will lead to a remote denial of service attack via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17722 |
409,168 | exiv2 | 1647908e00a4df7246d76678e59587e62c690dcd | https://github.com/Exiv2/exiv2 | https://github.com/Exiv2/exiv2/commit/1647908e00a4df7246d76678e59587e62c690dcd | fix for crash in bigtiff (issue #208) | 0 | Header readHeader(BasicIo& io)
{
byte header[2];
io.read(header, 2);
ByteOrder byteOrder = invalidByteOrder;
if (header[0] == 'I' && header[1] == 'I')
byteOrder = littleEndian;
else if (header[0] == 'M' && header[1] == 'M')
... | 165,654,027,073,115,680,000,000,000,000,000,000,000 | bigtiffimage.cpp | 337,082,523,884,149,800,000,000,000,000,000,000,000 | [
"CWE-617"
] | CVE-2017-17722 | In Exiv2 0.26, there is a reachable assertion in the readHeader function in bigtiffimage.cpp, which will lead to a remote denial of service attack via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2017-17722 |
208,384 | curl | 7214288898f5625a6cc196e22a74232eada7861c | https://github.com/curl/curl | https://github.com/curl/curl/commit/7214288898f5625a6cc196e22a74232eada7861c | transfer: strip credentials from the auto-referer header field
Added test 2081 to verify.
CVE-2021-22876
Bug: https://curl.se/docs/CVE-2021-22876.html | 1 | CURLcode Curl_follow(struct Curl_easy *data,
char *newurl, /* the Location: string */
followtype type) /* see transfer.h */
{
#ifdef CURL_DISABLE_HTTP
(void)data;
(void)newurl;
(void)type;
/* Location: following will not happen when HTTP is disabled */
return CURLE... | 83,044,627,888,364,720,000,000,000,000,000,000,000 | transfer.c | 250,080,327,778,362,250,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2021-22876 | curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP re... | https://nvd.nist.gov/vuln/detail/CVE-2021-22876 |
409,171 | curl | 7214288898f5625a6cc196e22a74232eada7861c | https://github.com/curl/curl | https://github.com/curl/curl/commit/7214288898f5625a6cc196e22a74232eada7861c | transfer: strip credentials from the auto-referer header field
Added test 2081 to verify.
CVE-2021-22876
Bug: https://curl.se/docs/CVE-2021-22876.html | 0 | CURLcode Curl_follow(struct Curl_easy *data,
char *newurl, /* the Location: string */
followtype type) /* see transfer.h */
{
#ifdef CURL_DISABLE_HTTP
(void)data;
(void)newurl;
(void)type;
/* Location: following will not happen when HTTP is disabled */
return CURLE... | 338,505,755,378,201,700,000,000,000,000,000,000,000 | transfer.c | 262,492,174,812,945,000,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2021-22876 | curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP re... | https://nvd.nist.gov/vuln/detail/CVE-2021-22876 |
208,389 | abrt | a6cdfd6a16251447264d203e145624a96fa811e3 | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/a6cdfd6a16251447264d203e145624a96fa811e3 | ccpp: add support for containers
A process is considered to be containerized when:
- has the 'container' env variable set to some value
- or has the 'container_uuid' env variable set to some value
- or has remounted /
Signed-off-by: Jakub Filak <jfilak@redhat.com> | 1 | int main(int argc, char** argv)
{
/* Kernel starts us with all fd's closed.
* But it's dangerous:
* fprintf(stderr) can dump messages into random fds, etc.
* Ensure that if any of fd 0,1,2 is closed, we open it to /dev/null.
*/
int fd = xopen("/dev/null", O_RDWR);
while (fd < 2)
... | 217,726,195,250,763,000,000,000,000,000,000,000,000 | abrt-hook-ccpp.c | 130,619,288,349,144,680,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-1862 | The crash reporting feature in Abrt allows local users to gain privileges by leveraging an execve by root after a chroot into a user-specified directory in a namedspaced environment. | https://nvd.nist.gov/vuln/detail/CVE-2015-1862 |
409,230 | abrt | a6cdfd6a16251447264d203e145624a96fa811e3 | https://github.com/abrt/abrt | https://github.com/abrt/abrt/commit/a6cdfd6a16251447264d203e145624a96fa811e3 | ccpp: add support for containers
A process is considered to be containerized when:
- has the 'container' env variable set to some value
- or has the 'container_uuid' env variable set to some value
- or has remounted /
Signed-off-by: Jakub Filak <jfilak@redhat.com> | 0 | int main(int argc, char** argv)
{
/* Kernel starts us with all fd's closed.
* But it's dangerous:
* fprintf(stderr) can dump messages into random fds, etc.
* Ensure that if any of fd 0,1,2 is closed, we open it to /dev/null.
*/
int fd = xopen("/dev/null", O_RDWR);
while (fd < 2)
... | 12,449,592,779,116,195,000,000,000,000,000,000,000 | abrt-hook-ccpp.c | 186,709,588,003,303,500,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2015-1862 | The crash reporting feature in Abrt allows local users to gain privileges by leveraging an execve by root after a chroot into a user-specified directory in a namedspaced environment. | https://nvd.nist.gov/vuln/detail/CVE-2015-1862 |
208,392 | qemu | 65d35a09979e63541afc5bfc595b9f1b1b4ae069 | https://github.com/bonzini/qemu | http://git.kernel.dk/?p=qemu.git;a=commitdiff;h=65d35a09979e63541afc5bfc595b9f1b1b4ae069 | CVE-2008-4539: fix a heap overflow in Cirrus emulation
The code in hw/cirrus_vga.c has changed a lot between CVE-2007-1320 has
been announced and the patch has been applied. As a consequence it has
wrongly applied and QEMU is still vulnerable to this bug if using VNC.
(noticed by Jan Niehusmann)
Signed-off-by: Aurel... | 1 | static int cirrus_bitblt_videotovideo_copy(CirrusVGAState * s)
{
if (s->ds->dpy_copy) {
cirrus_do_copy(s, s->cirrus_blt_dstaddr - s->start_addr,
s->cirrus_blt_srcaddr - s->start_addr,
s->cirrus_blt_width, s->cirrus_blt_height);
} else {
if (BLTUNSAFE(s))
return 0;
(*s->cirrus_r... | 42,414,772,514,992,535,000,000,000,000,000,000,000 | cirrus_vga.c | 127,568,660,777,291,270,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2007-1320 | Multiple heap-based buffer overflows in the cirrus_invalidate_region function in the Cirrus VGA extension in QEMU 0.8.2, as used in Xen and possibly other products, might allow local users to execute arbitrary code via unspecified vectors related to "attempting to mark non-existent regions as dirty," aka the "bitblt" h... | https://nvd.nist.gov/vuln/detail/CVE-2007-1320 |
409,235 | qemu | 65d35a09979e63541afc5bfc595b9f1b1b4ae069 | https://github.com/bonzini/qemu | http://git.kernel.dk/?p=qemu.git;a=commitdiff;h=65d35a09979e63541afc5bfc595b9f1b1b4ae069 | CVE-2008-4539: fix a heap overflow in Cirrus emulation
The code in hw/cirrus_vga.c has changed a lot between CVE-2007-1320 has
been announced and the patch has been applied. As a consequence it has
wrongly applied and QEMU is still vulnerable to this bug if using VNC.
(noticed by Jan Niehusmann)
Signed-off-by: Aurel... | 0 | static int cirrus_bitblt_videotovideo_copy(CirrusVGAState * s)
{
if (BLTUNSAFE(s))
return 0;
if (s->ds->dpy_copy) {
cirrus_do_copy(s, s->cirrus_blt_dstaddr - s->start_addr,
s->cirrus_blt_srcaddr - s->start_addr,
s->cirrus_blt_width, s->cirrus_blt_height);
} else {
(*s->cirrus_ro... | 68,618,513,806,201,910,000,000,000,000,000,000,000 | cirrus_vga.c | 25,868,057,476,701,274,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2007-1320 | Multiple heap-based buffer overflows in the cirrus_invalidate_region function in the Cirrus VGA extension in QEMU 0.8.2, as used in Xen and possibly other products, might allow local users to execute arbitrary code via unspecified vectors related to "attempting to mark non-existent regions as dirty," aka the "bitblt" h... | https://nvd.nist.gov/vuln/detail/CVE-2007-1320 |
208,402 | gst-plugins-good | 02174790726dd20a5c73ce2002189bf240ad4fe0 | https://github.com/GStreamer/gst-plugins-good | https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/commit/02174790726dd20a5c73ce2002189bf240ad4fe0?merge_request_iid=903 | matroskademux: Initialize track context out parameter to NULL before parsing
Various error return paths don't set it to NULL and callers are only
checking if the pointer is NULL. As it's allocated on the stack this
usually contains random stack memory, and more often than not the memory
of a previously parsed track.
... | 1 | gst_matroska_demux_parse_stream (GstMatroskaDemux * demux, GstEbmlRead * ebml,
GstMatroskaTrackContext ** dest_context)
{
GstMatroskaTrackContext *context;
GstCaps *caps = NULL;
GstTagList *cached_taglist;
GstFlowReturn ret;
guint32 id, riff_fourcc = 0;
guint16 riff_audio_fmt = 0;
gchar *codec = NULL;... | 203,605,486,912,847,120,000,000,000,000,000,000,000 | matroska-demux.c | 151,611,448,356,662,920,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3498 | GStreamer before 1.18.4 might cause heap corruption when parsing certain malformed Matroska files. | https://nvd.nist.gov/vuln/detail/CVE-2021-3498 |
409,272 | gst-plugins-good | 02174790726dd20a5c73ce2002189bf240ad4fe0 | https://github.com/GStreamer/gst-plugins-good | https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/commit/02174790726dd20a5c73ce2002189bf240ad4fe0?merge_request_iid=903 | matroskademux: Initialize track context out parameter to NULL before parsing
Various error return paths don't set it to NULL and callers are only
checking if the pointer is NULL. As it's allocated on the stack this
usually contains random stack memory, and more often than not the memory
of a previously parsed track.
... | 0 | gst_matroska_demux_parse_stream (GstMatroskaDemux * demux, GstEbmlRead * ebml,
GstMatroskaTrackContext ** dest_context)
{
GstMatroskaTrackContext *context;
GstCaps *caps = NULL;
GstTagList *cached_taglist;
GstFlowReturn ret;
guint32 id, riff_fourcc = 0;
guint16 riff_audio_fmt = 0;
gchar *codec = NULL;... | 264,811,927,925,942,170,000,000,000,000,000,000,000 | matroska-demux.c | 233,625,992,947,023,040,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-3498 | GStreamer before 1.18.4 might cause heap corruption when parsing certain malformed Matroska files. | https://nvd.nist.gov/vuln/detail/CVE-2021-3498 |
208,409 | mongo | c7f14b7be4a1f622fe81ef60f946a5aac17f3d0e | https://github.com/mongodb/mongo | https://github.com/mongodb/mongo/commit/c7f14b7be4a1f622fe81ef60f946a5aac17f3d0e | SERVER-49142 Validate correct field name in RoleName::parseFromBSON() | 1 | RoleName RoleName::parseFromBSON(const BSONElement& elem) {
auto obj = elem.embeddedObjectUserCheck();
std::array<BSONElement, 2> fields;
obj.getFields(
{AuthorizationManager::ROLE_NAME_FIELD_NAME, AuthorizationManager::ROLE_DB_FIELD_NAME},
&fields);
const auto& nameField = fields[0];
... | 149,200,813,351,437,200,000,000,000,000,000,000,000 | role_name.cpp | 282,049,995,007,922,200,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-7925 | Incorrect validation of user input in the role name parser may lead to use of uninitialized memory allowing an unauthenticated attacker to use a specially crafted request to cause a denial of service. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.0-rc12; v4.2 versions prior to 4.2.9. | https://nvd.nist.gov/vuln/detail/CVE-2020-7925 |
409,371 | mongo | c7f14b7be4a1f622fe81ef60f946a5aac17f3d0e | https://github.com/mongodb/mongo | https://github.com/mongodb/mongo/commit/c7f14b7be4a1f622fe81ef60f946a5aac17f3d0e | SERVER-49142 Validate correct field name in RoleName::parseFromBSON() | 0 | RoleName RoleName::parseFromBSON(const BSONElement& elem) {
auto obj = elem.embeddedObjectUserCheck();
std::array<BSONElement, 2> fields;
obj.getFields(
{AuthorizationManager::ROLE_NAME_FIELD_NAME, AuthorizationManager::ROLE_DB_FIELD_NAME},
&fields);
const auto& nameField = fields[0];
... | 255,183,519,060,062,900,000,000,000,000,000,000,000 | role_name.cpp | 70,546,637,693,182,840,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2020-7925 | Incorrect validation of user input in the role name parser may lead to use of uninitialized memory allowing an unauthenticated attacker to use a specially crafted request to cause a denial of service. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.0-rc12; v4.2 versions prior to 4.2.9. | https://nvd.nist.gov/vuln/detail/CVE-2020-7925 |
208,410 | linux | ead16e53c2f0ed946d82d4037c630e2f60f4ab69 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ead16e53c2f0ed946d82d4037c630e2f60f4ab69 | can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices
Uninitialized Kernel memory can leak to USB devices.
Fix by using kzalloc() instead of kmalloc() on the affected buffers.
Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
Reported-by: syzbot+d6a5a1a3657b596ef132@syzkaller.appspotmail.com
Fixes: f14e2243... | 1 | static int pcan_usb_pro_drv_loaded(struct peak_usb_device *dev, int loaded)
{
u8 *buffer;
int err;
buffer = kmalloc(PCAN_USBPRO_FCT_DRVLD_REQ_LEN, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
buffer[0] = 0;
buffer[1] = !!loaded;
err = pcan_usb_pro_send_req(dev, PCAN_USBPRO_REQ_FCT,
PCAN_USBPRO_FCT_DRVL... | 18,392,522,369,682,705,000,000,000,000,000,000,000 | pcan_usb_pro.c | 317,739,464,164,599,700,000,000,000,000,000,000,000 | [
"CWE-909"
] | CVE-2019-19536 | In the Linux kernel before 5.2.9, there is an info-leak bug that can be caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_pro.c driver, aka CID-ead16e53c2f0. | https://nvd.nist.gov/vuln/detail/CVE-2019-19536 |
409,389 | linux | ead16e53c2f0ed946d82d4037c630e2f60f4ab69 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ead16e53c2f0ed946d82d4037c630e2f60f4ab69 | can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices
Uninitialized Kernel memory can leak to USB devices.
Fix by using kzalloc() instead of kmalloc() on the affected buffers.
Signed-off-by: Tomas Bortoli <tomasbortoli@gmail.com>
Reported-by: syzbot+d6a5a1a3657b596ef132@syzkaller.appspotmail.com
Fixes: f14e2243... | 0 | static int pcan_usb_pro_drv_loaded(struct peak_usb_device *dev, int loaded)
{
u8 *buffer;
int err;
buffer = kzalloc(PCAN_USBPRO_FCT_DRVLD_REQ_LEN, GFP_KERNEL);
if (!buffer)
return -ENOMEM;
buffer[0] = 0;
buffer[1] = !!loaded;
err = pcan_usb_pro_send_req(dev, PCAN_USBPRO_REQ_FCT,
PCAN_USBPRO_FCT_DRVL... | 49,492,780,223,943,620,000,000,000,000,000,000,000 | pcan_usb_pro.c | 108,852,552,708,594,500,000,000,000,000,000,000,000 | [
"CWE-909"
] | CVE-2019-19536 | In the Linux kernel before 5.2.9, there is an info-leak bug that can be caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_pro.c driver, aka CID-ead16e53c2f0. | https://nvd.nist.gov/vuln/detail/CVE-2019-19536 |
208,423 | linux | a21b7f0cff1906a93a0130b74713b15a0b36481d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a21b7f0cff1906a93a0130b74713b15a0b36481d | net: qrtr: fix memort leak in qrtr_tun_write_iter
In qrtr_tun_write_iter the allocated kbuf should be release in case of
error or success return.
v2 Update: Thanks to David Miller for pointing out the release on success
path as well.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Signed-off-by: David S. ... | 1 | static ssize_t qrtr_tun_write_iter(struct kiocb *iocb, struct iov_iter *from)
{
struct file *filp = iocb->ki_filp;
struct qrtr_tun *tun = filp->private_data;
size_t len = iov_iter_count(from);
ssize_t ret;
void *kbuf;
kbuf = kzalloc(len, GFP_KERNEL);
if (!kbuf)
return -ENOMEM;
if (!copy_from_iter_full(kbuf,... | 2,549,043,521,370,202,800,000,000,000,000,000,000 | tun.c | 81,654,701,115,515,440,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19079 | A memory leak in the qrtr_tun_write_iter() function in net/qrtr/tun.c in the Linux kernel before 5.3 allows attackers to cause a denial of service (memory consumption), aka CID-a21b7f0cff19. | https://nvd.nist.gov/vuln/detail/CVE-2019-19079 |
409,713 | linux | a21b7f0cff1906a93a0130b74713b15a0b36481d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a21b7f0cff1906a93a0130b74713b15a0b36481d | net: qrtr: fix memort leak in qrtr_tun_write_iter
In qrtr_tun_write_iter the allocated kbuf should be release in case of
error or success return.
v2 Update: Thanks to David Miller for pointing out the release on success
path as well.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Signed-off-by: David S. ... | 0 | static ssize_t qrtr_tun_write_iter(struct kiocb *iocb, struct iov_iter *from)
{
struct file *filp = iocb->ki_filp;
struct qrtr_tun *tun = filp->private_data;
size_t len = iov_iter_count(from);
ssize_t ret;
void *kbuf;
kbuf = kzalloc(len, GFP_KERNEL);
if (!kbuf)
return -ENOMEM;
if (!copy_from_iter_full(kbuf,... | 166,963,405,477,832,430,000,000,000,000,000,000,000 | tun.c | 192,309,659,833,973,330,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19079 | A memory leak in the qrtr_tun_write_iter() function in net/qrtr/tun.c in the Linux kernel before 5.3 allows attackers to cause a denial of service (memory consumption), aka CID-a21b7f0cff19. | https://nvd.nist.gov/vuln/detail/CVE-2019-19079 |
208,424 | linux | dbcc7d57bffc0c8cac9dac11bec548597d59a6a5 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbcc7d57bffc0c8cac9dac11bec548597d59a6a5 | btrfs: fix race when cloning extent buffer during rewind of an old root
While resolving backreferences, as part of a logical ino ioctl call or
fiemap, we can end up hitting a BUG_ON() when replaying tree mod log
operations of a root, triggering a stack trace like the following:
------------[ cut here ]------------
... | 1 | get_old_root(struct btrfs_root *root, u64 time_seq)
{
struct btrfs_fs_info *fs_info = root->fs_info;
struct tree_mod_elem *tm;
struct extent_buffer *eb = NULL;
struct extent_buffer *eb_root;
u64 eb_root_owner = 0;
struct extent_buffer *old;
struct tree_mod_root *old_root = NULL;
u64 old_generation = 0;
u64 log... | 183,573,493,479,480,760,000,000,000,000,000,000,000 | ctree.c | 34,395,934,875,194,930,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2021-28964 | A race condition was discovered in get_old_root in fs/btrfs/ctree.c in the Linux kernel through 5.11.8. It allows attackers to cause a denial of service (BUG) because of a lack of locking on an extent buffer before a cloning operation, aka CID-dbcc7d57bffc. | https://nvd.nist.gov/vuln/detail/CVE-2021-28964 |
409,779 | linux | dbcc7d57bffc0c8cac9dac11bec548597d59a6a5 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbcc7d57bffc0c8cac9dac11bec548597d59a6a5 | btrfs: fix race when cloning extent buffer during rewind of an old root
While resolving backreferences, as part of a logical ino ioctl call or
fiemap, we can end up hitting a BUG_ON() when replaying tree mod log
operations of a root, triggering a stack trace like the following:
------------[ cut here ]------------
... | 0 | get_old_root(struct btrfs_root *root, u64 time_seq)
{
struct btrfs_fs_info *fs_info = root->fs_info;
struct tree_mod_elem *tm;
struct extent_buffer *eb = NULL;
struct extent_buffer *eb_root;
u64 eb_root_owner = 0;
struct extent_buffer *old;
struct tree_mod_root *old_root = NULL;
u64 old_generation = 0;
u64 log... | 313,604,560,058,958,300,000,000,000,000,000,000,000 | ctree.c | 282,447,862,351,222,720,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2021-28964 | A race condition was discovered in get_old_root in fs/btrfs/ctree.c in the Linux kernel through 5.11.8. It allows attackers to cause a denial of service (BUG) because of a lack of locking on an extent buffer before a cloning operation, aka CID-dbcc7d57bffc. | https://nvd.nist.gov/vuln/detail/CVE-2021-28964 |
208,431 | linux | 36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | GFS2: don't set rgrp gl_object until it's inserted into rgrp tree
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the rgrp into
the rgrp rbtree. The problem is: if another process was also reading
the rgrp in, and had already inserted its newly create... | 1 | static int read_rindex_entry(struct gfs2_inode *ip)
{
struct gfs2_sbd *sdp = GFS2_SB(&ip->i_inode);
const unsigned bsize = sdp->sd_sb.sb_bsize;
loff_t pos = sdp->sd_rgrps * sizeof(struct gfs2_rindex);
struct gfs2_rindex buf;
int error;
struct gfs2_rgrpd *rgd;
if (pos >= i_size_read(&ip->i_inode))
return 1;
... | 252,897,794,735,677,800,000,000,000,000,000,000,000 | rgrp.c | 84,056,968,392,408,675,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10905 | An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8. A use-after-free is caused by the functions gfs2_clear_rgrpd and read_rindex_entry. | https://nvd.nist.gov/vuln/detail/CVE-2016-10905 |
410,102 | linux | 36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | GFS2: don't set rgrp gl_object until it's inserted into rgrp tree
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the rgrp into
the rgrp rbtree. The problem is: if another process was also reading
the rgrp in, and had already inserted its newly create... | 0 | static int read_rindex_entry(struct gfs2_inode *ip)
{
struct gfs2_sbd *sdp = GFS2_SB(&ip->i_inode);
const unsigned bsize = sdp->sd_sb.sb_bsize;
loff_t pos = sdp->sd_rgrps * sizeof(struct gfs2_rindex);
struct gfs2_rindex buf;
int error;
struct gfs2_rgrpd *rgd;
if (pos >= i_size_read(&ip->i_inode))
return 1;
... | 234,298,165,096,376,730,000,000,000,000,000,000,000 | rgrp.c | 280,860,498,314,502,500,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10905 | An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8. A use-after-free is caused by the functions gfs2_clear_rgrpd and read_rindex_entry. | https://nvd.nist.gov/vuln/detail/CVE-2016-10905 |
208,432 | linux | 36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | GFS2: don't set rgrp gl_object until it's inserted into rgrp tree
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the rgrp into
the rgrp rbtree. The problem is: if another process was also reading
the rgrp in, and had already inserted its newly create... | 1 | void gfs2_clear_rgrpd(struct gfs2_sbd *sdp)
{
struct rb_node *n;
struct gfs2_rgrpd *rgd;
struct gfs2_glock *gl;
while ((n = rb_first(&sdp->sd_rindex_tree))) {
rgd = rb_entry(n, struct gfs2_rgrpd, rd_node);
gl = rgd->rd_gl;
rb_erase(n, &sdp->sd_rindex_tree);
if (gl) {
spin_lock(&gl->gl_lockref.lock);
... | 157,091,507,671,994,680,000,000,000,000,000,000,000 | rgrp.c | 84,056,968,392,408,675,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10905 | An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8. A use-after-free is caused by the functions gfs2_clear_rgrpd and read_rindex_entry. | https://nvd.nist.gov/vuln/detail/CVE-2016-10905 |
410,094 | linux | 36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4ad0316c017d5b271378ed9a1c9a4b77fab5f | GFS2: don't set rgrp gl_object until it's inserted into rgrp tree
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the rgrp into
the rgrp rbtree. The problem is: if another process was also reading
the rgrp in, and had already inserted its newly create... | 0 | void gfs2_clear_rgrpd(struct gfs2_sbd *sdp)
{
struct rb_node *n;
struct gfs2_rgrpd *rgd;
struct gfs2_glock *gl;
while ((n = rb_first(&sdp->sd_rindex_tree))) {
rgd = rb_entry(n, struct gfs2_rgrpd, rd_node);
gl = rgd->rd_gl;
rb_erase(n, &sdp->sd_rindex_tree);
if (gl) {
spin_lock(&gl->gl_lockref.lock);
... | 57,875,066,619,980,080,000,000,000,000,000,000 | rgrp.c | 280,860,498,314,502,500,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2016-10905 | An issue was discovered in fs/gfs2/rgrp.c in the Linux kernel before 4.8. A use-after-free is caused by the functions gfs2_clear_rgrpd and read_rindex_entry. | https://nvd.nist.gov/vuln/detail/CVE-2016-10905 |
208,434 | mod_auth_openidc | 03e6bfb446f4e3f27c003d30d6a433e5dd8e2b3d | https://github.com/zmartzone/mod_auth_openidc | https://github.com/zmartzone/mod_auth_openidc/commit/03e6bfb446f4e3f27c003d30d6a433e5dd8e2b3d | apply OIDCRedirectURLsAllowed setting to target_link_uri
closes #672; thanks @Meheni
release 2.4.9.4
Signed-off-by: Hans Zandbelt <hans.zandbelt@zmartzone.eu> | 1 | static int oidc_handle_discovery_response(request_rec *r, oidc_cfg *c) {
/* variables to hold the values returned in the response */
char *issuer = NULL, *target_link_uri = NULL, *login_hint = NULL,
*auth_request_params = NULL, *csrf_cookie, *csrf_query = NULL,
*user = NULL, *path_scopes;
oidc_provider_t *pro... | 185,916,868,323,944,120,000,000,000,000,000,000,000 | mod_auth_openidc.c | 157,714,869,901,486,540,000,000,000,000,000,000,000 | [
"CWE-601"
] | CVE-2021-39191 | mod_auth_openidc is an authentication/authorization module for the Apache 2.x HTTP server that functions as an OpenID Connect Relying Party, authenticating users against an OpenID Connect Provider. In versions prior to 2.4.9.4, the 3rd-party init SSO functionality of mod_auth_openidc was reported to be vulnerable to an... | https://nvd.nist.gov/vuln/detail/CVE-2021-39191 |
410,158 | mod_auth_openidc | 03e6bfb446f4e3f27c003d30d6a433e5dd8e2b3d | https://github.com/zmartzone/mod_auth_openidc | https://github.com/zmartzone/mod_auth_openidc/commit/03e6bfb446f4e3f27c003d30d6a433e5dd8e2b3d | apply OIDCRedirectURLsAllowed setting to target_link_uri
closes #672; thanks @Meheni
release 2.4.9.4
Signed-off-by: Hans Zandbelt <hans.zandbelt@zmartzone.eu> | 0 | static int oidc_handle_discovery_response(request_rec *r, oidc_cfg *c) {
/* variables to hold the values returned in the response */
char *issuer = NULL, *target_link_uri = NULL, *login_hint = NULL,
*auth_request_params = NULL, *csrf_cookie, *csrf_query = NULL,
*user = NULL, *path_scopes;
oidc_provider_t *pro... | 299,402,996,315,821,320,000,000,000,000,000,000,000 | mod_auth_openidc.c | 297,685,906,617,947,850,000,000,000,000,000,000,000 | [
"CWE-601"
] | CVE-2021-39191 | mod_auth_openidc is an authentication/authorization module for the Apache 2.x HTTP server that functions as an OpenID Connect Relying Party, authenticating users against an OpenID Connect Provider. In versions prior to 2.4.9.4, the 3rd-party init SSO functionality of mod_auth_openidc was reported to be vulnerable to an... | https://nvd.nist.gov/vuln/detail/CVE-2021-39191 |
208,437 | linux | 513f86d73855ce556ea9522b6bfd79f87356dc3a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=513f86d73855ce556ea9522b6bfd79f87356dc3a | ext4: always verify the magic number in xattr blocks
If there an inode points to a block which is also some other type of
metadata block (such as a block allocation bitmap), the
buffer_verified flag can be set when it was validated as that other
metadata block type; however, it would make a really terrible external
at... | 1 | __ext4_xattr_check_block(struct inode *inode, struct buffer_head *bh,
const char *function, unsigned int line)
{
int error = -EFSCORRUPTED;
if (buffer_verified(bh))
return 0;
if (BHDR(bh)->h_magic != cpu_to_le32(EXT4_XATTR_MAGIC) ||
BHDR(bh)->h_blocks != cpu_to_le32(1))
goto errout;
error = -EFSBADCR... | 129,202,135,438,693,670,000,000,000,000,000,000,000 | xattr.c | 286,039,824,774,724,880,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-10879 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause a use-after-free in ext4_xattr_set_entry function and a denial of service or unspecified other impact may occur by renaming a file in a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10879 |
410,229 | linux | 513f86d73855ce556ea9522b6bfd79f87356dc3a | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=513f86d73855ce556ea9522b6bfd79f87356dc3a | ext4: always verify the magic number in xattr blocks
If there an inode points to a block which is also some other type of
metadata block (such as a block allocation bitmap), the
buffer_verified flag can be set when it was validated as that other
metadata block type; however, it would make a really terrible external
at... | 0 | __ext4_xattr_check_block(struct inode *inode, struct buffer_head *bh,
const char *function, unsigned int line)
{
int error = -EFSCORRUPTED;
if (BHDR(bh)->h_magic != cpu_to_le32(EXT4_XATTR_MAGIC) ||
BHDR(bh)->h_blocks != cpu_to_le32(1))
goto errout;
if (buffer_verified(bh))
return 0;
error = -EFSBADCR... | 315,014,257,302,834,900,000,000,000,000,000,000,000 | xattr.c | 256,578,085,620,066,300,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2018-10879 | A flaw was found in the Linux kernel's ext4 filesystem. A local user can cause a use-after-free in ext4_xattr_set_entry function and a denial of service or unspecified other impact may occur by renaming a file in a crafted ext4 filesystem image. | https://nvd.nist.gov/vuln/detail/CVE-2018-10879 |
208,440 | ImageMagick | 19dbe11c5060f66abb393d1945107c5f54894fa8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/19dbe11c5060f66abb393d1945107c5f54894fa8 | https://github.com/ImageMagick/ImageMagick/issues/679 | 1 | static MagickBooleanType load_level(Image *image,XCFDocInfo *inDocInfo,
XCFLayerInfo *inLayerInfo,ExceptionInfo *exception)
{
int
destLeft = 0,
destTop = 0;
Image*
tile_image;
MagickBooleanType
status;
MagickOffsetType
saved_pos,
offset,
offset2;
register ssize_t
i;
si... | 39,792,828,950,217,595,000,000,000,000,000,000,000 | xcf.c | 251,228,203,542,098,800,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2017-13133 | In ImageMagick 7.0.6-8, the load_level function in coders/xcf.c lacks offset validation, which allows attackers to cause a denial of service (load_tile memory exhaustion) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-13133 |
410,260 | ImageMagick | 19dbe11c5060f66abb393d1945107c5f54894fa8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/19dbe11c5060f66abb393d1945107c5f54894fa8 | https://github.com/ImageMagick/ImageMagick/issues/679 | 0 | static MagickBooleanType load_level(Image *image,XCFDocInfo *inDocInfo,
XCFLayerInfo *inLayerInfo,ExceptionInfo *exception)
{
int
destLeft = 0,
destTop = 0;
Image*
tile_image;
MagickBooleanType
status;
MagickOffsetType
saved_pos,
offset,
offset2;
register ssize_t
i;
si... | 138,141,454,496,072,490,000,000,000,000,000,000,000 | xcf.c | 281,855,954,091,640,860,000,000,000,000,000,000,000 | [
"CWE-770"
] | CVE-2017-13133 | In ImageMagick 7.0.6-8, the load_level function in coders/xcf.c lacks offset validation, which allows attackers to cause a denial of service (load_tile memory exhaustion) via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2017-13133 |
208,441 | linux | 34b3be18a04ecdc610aae4c48e5d1b799d8689f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/34b3be18a04ecdc610aae4c48e5d1b799d8689f6 | RDMA/hfi1: Prevent memory leak in sdma_init
In sdma_init if rhashtable_init fails the allocated memory for
tmp_sdma_rht should be released.
Fixes: 5a52a7acf7e2 ("IB/hfi1: NULL pointer dereference when freeing rhashtable")
Link: https://lore.kernel.org/r/20190925144543.10141-1-navid.emamdoost@gmail.com
Signed-off-by: ... | 1 | int sdma_init(struct hfi1_devdata *dd, u8 port)
{
unsigned this_idx;
struct sdma_engine *sde;
struct rhashtable *tmp_sdma_rht;
u16 descq_cnt;
void *curr_head;
struct hfi1_pportdata *ppd = dd->pport + port;
u32 per_sdma_credits;
uint idle_cnt = sdma_idle_cnt;
size_t num_engines = chip_sdma_engines(dd);
int ret... | 283,222,123,785,724,780,000,000,000,000,000,000,000 | sdma.c | 278,743,909,233,214,100,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19065 | A memory leak in the sdma_init() function in drivers/infiniband/hw/hfi1/sdma.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering rhashtable_init() failures, aka CID-34b3be18a04e. NOTE: This has been disputed as not a vulnerability because "rhashtable_init(... | https://nvd.nist.gov/vuln/detail/CVE-2019-19065 |
410,329 | linux | 34b3be18a04ecdc610aae4c48e5d1b799d8689f6 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/34b3be18a04ecdc610aae4c48e5d1b799d8689f6 | RDMA/hfi1: Prevent memory leak in sdma_init
In sdma_init if rhashtable_init fails the allocated memory for
tmp_sdma_rht should be released.
Fixes: 5a52a7acf7e2 ("IB/hfi1: NULL pointer dereference when freeing rhashtable")
Link: https://lore.kernel.org/r/20190925144543.10141-1-navid.emamdoost@gmail.com
Signed-off-by: ... | 0 | int sdma_init(struct hfi1_devdata *dd, u8 port)
{
unsigned this_idx;
struct sdma_engine *sde;
struct rhashtable *tmp_sdma_rht;
u16 descq_cnt;
void *curr_head;
struct hfi1_pportdata *ppd = dd->pport + port;
u32 per_sdma_credits;
uint idle_cnt = sdma_idle_cnt;
size_t num_engines = chip_sdma_engines(dd);
int ret... | 327,294,522,245,869,700,000,000,000,000,000,000,000 | sdma.c | 223,095,793,489,069,440,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-19065 | A memory leak in the sdma_init() function in drivers/infiniband/hw/hfi1/sdma.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption) by triggering rhashtable_init() failures, aka CID-34b3be18a04e. NOTE: This has been disputed as not a vulnerability because "rhashtable_init(... | https://nvd.nist.gov/vuln/detail/CVE-2019-19065 |
208,444 | Pillow | c50ebe6459a131a1ea8ca531f10da616d3ceaa0f | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/c50ebe6459a131a1ea8ca531f10da616d3ceaa0f | Map.c overflow fixes | 1 | PyImaging_MapBuffer(PyObject* self, PyObject* args)
{
Py_ssize_t y, size;
Imaging im;
PyObject* target;
Py_buffer view;
char* mode;
char* codec;
PyObject* bbox;
Py_ssize_t offset;
int xsize, ysize;
int stride;
int ystep;
if (!PyArg_ParseTuple(args, "O(ii)sOn(sii)", &tar... | 176,958,146,727,139,320,000,000,000,000,000,000,000 | map.c | 40,916,785,765,586,700,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9189 | Pillow before 3.3.2 allows context-dependent attackers to obtain sensitive information by using the "crafted image file" approach, related to an "Integer Overflow" issue affecting the Image.core.map_buffer in map.c component. | https://nvd.nist.gov/vuln/detail/CVE-2016-9189 |
410,445 | Pillow | c50ebe6459a131a1ea8ca531f10da616d3ceaa0f | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/c50ebe6459a131a1ea8ca531f10da616d3ceaa0f | Map.c overflow fixes | 0 | PyImaging_MapBuffer(PyObject* self, PyObject* args)
{
Py_ssize_t y, size;
Imaging im;
PyObject* target;
Py_buffer view;
char* mode;
char* codec;
PyObject* bbox;
Py_ssize_t offset;
int xsize, ysize;
int stride;
int ystep;
if (!PyArg_ParseTuple(args, "O(ii)sOn(sii)", &tar... | 76,344,934,119,998,150,000,000,000,000,000,000,000 | map.c | 132,057,866,853,055,070,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2016-9189 | Pillow before 3.3.2 allows context-dependent attackers to obtain sensitive information by using the "crafted image file" approach, related to an "Integer Overflow" issue affecting the Image.core.map_buffer in map.c component. | https://nvd.nist.gov/vuln/detail/CVE-2016-9189 |
208,445 | claws | e3ffcb455e0376053451ce968e6c71ef37708222 | http://git.claws-mail.org/?p=claws | http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=e3ffcb455e0376053451ce968e6c71ef37708222 | fix bug 3584, 'After 3.13.1, characters in some Japanese codec are never correctly converted to internal ones'
Thanks to honda@math.sci.hokudai.ac.jp | 1 | static gint conv_jistoeuc(gchar *outbuf, gint outlen, const gchar *inbuf)
{
const guchar *in = inbuf;
gchar *out = outbuf;
JISState state = JIS_ASCII;
while (*in != '\0' && (out - outbuf) > outlen - 3) {
if (*in == ESC) {
in++;
if (*in == '$') {
if (*(in + 1) == '@' || *(in + 1) == 'B') {
state = ... | 252,115,485,394,894,700,000,000,000,000,000,000,000 | codeconv.c | 293,968,961,442,628,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8614 | Multiple stack-based buffer overflows in the (1) conv_jistoeuc, (2) conv_euctojis, and (3) conv_sjistoeuc functions in codeconv.c in Claws Mail before 3.13.1 allow remote attackers to have unspecified impact via a crafted email, involving Japanese character set conversion. | https://nvd.nist.gov/vuln/detail/CVE-2015-8614 |
410,455 | claws | e3ffcb455e0376053451ce968e6c71ef37708222 | http://git.claws-mail.org/?p=claws | http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=e3ffcb455e0376053451ce968e6c71ef37708222 | fix bug 3584, 'After 3.13.1, characters in some Japanese codec are never correctly converted to internal ones'
Thanks to honda@math.sci.hokudai.ac.jp | 0 | static gint conv_jistoeuc(gchar *outbuf, gint outlen, const gchar *inbuf)
{
const guchar *in = inbuf;
gchar *out = outbuf;
JISState state = JIS_ASCII;
while (*in != '\0' && (out - outbuf) < outlen - 3) {
if (*in == ESC) {
in++;
if (*in == '$') {
if (*(in + 1) == '@' || *(in + 1) == 'B') {
state = ... | 205,962,140,475,651,100,000,000,000,000,000,000,000 | codeconv.c | 17,394,752,616,039,273,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-8614 | Multiple stack-based buffer overflows in the (1) conv_jistoeuc, (2) conv_euctojis, and (3) conv_sjistoeuc functions in codeconv.c in Claws Mail before 3.13.1 allow remote attackers to have unspecified impact via a crafted email, involving Japanese character set conversion. | https://nvd.nist.gov/vuln/detail/CVE-2015-8614 |
208,449 | php-src | e617f03066ce81d26f56c06d6bd7787c7de08703 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=e617f03066ce81d26f56c06d6bd7787c7de08703 | Fix #77367: Negative size parameter in mb_split
When adding the last element to the result value of `mb_split`, the
`chunk_pos` may point beyond the end of the string, in which case the
unsigned `n` would underflow. Therefore, we check whether this is the
case in the first place, and only calculate `n` otherwise. Si... | 1 | PHP_FUNCTION(mb_split)
{
char *arg_pattern;
size_t arg_pattern_len;
php_mb_regex_t *re;
OnigRegion *regs = NULL;
char *string;
OnigUChar *pos, *chunk_pos;
size_t string_len;
int err;
size_t n;
zend_long count = -1;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "ss|l", &arg_pattern, &arg_pattern_len, &string, ... | 78,060,171,719,889,460,000,000,000,000,000,000,000 | php_mbregex.c | 107,472,818,155,514,620,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-9025 | An issue was discovered in PHP 7.3.x before 7.3.1. An invalid multibyte string supplied as an argument to the mb_split() function in ext/mbstring/php_mbregex.c can cause PHP to execute memcpy() with a negative argument, which could read and write past buffers allocated for the data. | https://nvd.nist.gov/vuln/detail/CVE-2019-9025 |
410,543 | php-src | e617f03066ce81d26f56c06d6bd7787c7de08703 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=e617f03066ce81d26f56c06d6bd7787c7de08703 | Fix #77367: Negative size parameter in mb_split
When adding the last element to the result value of `mb_split`, the
`chunk_pos` may point beyond the end of the string, in which case the
unsigned `n` would underflow. Therefore, we check whether this is the
case in the first place, and only calculate `n` otherwise. Si... | 0 | PHP_FUNCTION(mb_split)
{
char *arg_pattern;
size_t arg_pattern_len;
php_mb_regex_t *re;
OnigRegion *regs = NULL;
char *string;
OnigUChar *pos, *chunk_pos;
size_t string_len;
int err;
zend_long count = -1;
if (zend_parse_parameters(ZEND_NUM_ARGS(), "ss|l", &arg_pattern, &arg_pattern_len, &string, &string_len... | 17,117,505,874,798,762,000,000,000,000,000,000,000 | php_mbregex.c | 293,341,158,024,117,600,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-9025 | An issue was discovered in PHP 7.3.x before 7.3.1. An invalid multibyte string supplied as an argument to the mb_split() function in ext/mbstring/php_mbregex.c can cause PHP to execute memcpy() with a negative argument, which could read and write past buffers allocated for the data. | https://nvd.nist.gov/vuln/detail/CVE-2019-9025 |
208,450 | linux | 780e982905bef61d13496d9af5310bf4af3a64d3 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=780e982905bef61d13496d9af5310bf4af3a64d3 | RDS: validate the requested traces user input against max supported
Larger than supported value can lead to array read/write overflow.
Reported-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | static int rds_recv_track_latency(struct rds_sock *rs, char __user *optval,
int optlen)
{
struct rds_rx_trace_so trace;
int i;
if (optlen != sizeof(struct rds_rx_trace_so))
return -EFAULT;
if (copy_from_user(&trace, optval, sizeof(trace)))
return -EFAULT;
rs->rs_rx_traces = trace.rx_traces;
for (i = ... | 288,246,883,071,528,500,000,000,000,000,000,000,000 | af_rds.c | 338,518,426,638,068,100,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-18552 | An issue was discovered in net/rds/af_rds.c in the Linux kernel before 4.11. There is an out of bounds write and read in the function rds_recv_track_latency. | https://nvd.nist.gov/vuln/detail/CVE-2017-18552 |
410,563 | linux | 780e982905bef61d13496d9af5310bf4af3a64d3 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=780e982905bef61d13496d9af5310bf4af3a64d3 | RDS: validate the requested traces user input against max supported
Larger than supported value can lead to array read/write overflow.
Reported-by: Colin Ian King <colin.king@canonical.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net> | 0 | static int rds_recv_track_latency(struct rds_sock *rs, char __user *optval,
int optlen)
{
struct rds_rx_trace_so trace;
int i;
if (optlen != sizeof(struct rds_rx_trace_so))
return -EFAULT;
if (copy_from_user(&trace, optval, sizeof(trace)))
return -EFAULT;
if (trace.rx_traces > RDS_MSG_RX_DGRAM_TRACE_M... | 328,636,589,633,239,400,000,000,000,000,000,000,000 | af_rds.c | 89,101,999,641,160,390,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-18552 | An issue was discovered in net/rds/af_rds.c in the Linux kernel before 4.11. There is an out of bounds write and read in the function rds_recv_track_latency. | https://nvd.nist.gov/vuln/detail/CVE-2017-18552 |
208,485 | php-src | 6dbb1ee46b5f4725cc6519abf91e512a2a10dfed | https://github.com/php/php-src | https://github.com/php/php-src/commit/6dbb1ee46b5f4725cc6519abf91e512a2a10dfed?w=1 | Fixed bug #72627: Memory Leakage In exif_process_IFD_in_TIFF | 1 | static int exif_process_IFD_in_TIFF(image_info_type *ImageInfo, size_t dir_offset, int section_index TSRMLS_DC)
{
int i, sn, num_entries, sub_section_index = 0;
unsigned char *dir_entry;
char tagname[64];
size_t ifd_size, dir_size, entry_offset, next_offset, entry_length, entry_value=0, fgot;
int entry_tag , entry... | 107,067,358,638,280,860,000,000,000,000,000,000,000 | exif.c | 125,847,680,861,239,830,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-7128 | The exif_process_IFD_in_TIFF function in ext/exif/exif.c in PHP before 5.6.25 and 7.x before 7.0.10 mishandles the case of a thumbnail offset that exceeds the file size, which allows remote attackers to obtain sensitive information from process memory via a crafted TIFF image. | https://nvd.nist.gov/vuln/detail/CVE-2016-7128 |
411,766 | php-src | 6dbb1ee46b5f4725cc6519abf91e512a2a10dfed | https://github.com/php/php-src | https://github.com/php/php-src/commit/6dbb1ee46b5f4725cc6519abf91e512a2a10dfed?w=1 | Fixed bug #72627: Memory Leakage In exif_process_IFD_in_TIFF | 0 | static int exif_process_IFD_in_TIFF(image_info_type *ImageInfo, size_t dir_offset, int section_index TSRMLS_DC)
{
int i, sn, num_entries, sub_section_index = 0;
unsigned char *dir_entry;
char tagname[64];
size_t ifd_size, dir_size, entry_offset, next_offset, entry_length, entry_value=0, fgot;
int entry_tag , entry... | 72,234,440,876,195,380,000,000,000,000,000,000,000 | exif.c | 43,214,828,267,073,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-7128 | The exif_process_IFD_in_TIFF function in ext/exif/exif.c in PHP before 5.6.25 and 7.x before 7.0.10 mishandles the case of a thumbnail offset that exceeds the file size, which allows remote attackers to obtain sensitive information from process memory via a crafted TIFF image. | https://nvd.nist.gov/vuln/detail/CVE-2016-7128 |
208,488 | php-src | adc070ca995384e4de83fa3446c6dfcf946a3f50 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=adc070ca995384e4de83fa3446c6dfcf946a3f50 | fix typo in ODBC code | 1 | PHP_FUNCTION(odbc_execute)
{
zval *pv_res, *pv_param_arr, **tmp;
typedef struct params_t {
SQLLEN vallen;
int fp;
} params_t;
params_t *params = NULL;
char *filename;
unsigned char otype;
SQLSMALLINT sqltype, ctype, scale;
SQLSMALLINT nullable;
SQLULEN precision;
odbc_result *result;
int numArgs, ... | 194,763,470,601,050,400,000,000,000,000,000,000,000 | php_odbc.c | 324,624,632,588,735,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2006-7243 | PHP before 5.3.4 accepts the \0 character in a pathname, which might allow context-dependent attackers to bypass intended access restrictions by placing a safe file extension after this character, as demonstrated by .php\0.jpg at the end of the argument to the file_exists function. | https://nvd.nist.gov/vuln/detail/CVE-2006-7243 |
411,778 | php-src | adc070ca995384e4de83fa3446c6dfcf946a3f50 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=adc070ca995384e4de83fa3446c6dfcf946a3f50 | fix typo in ODBC code | 0 | PHP_FUNCTION(odbc_execute)
{
zval *pv_res, *pv_param_arr, **tmp;
typedef struct params_t {
SQLLEN vallen;
int fp;
} params_t;
params_t *params = NULL;
char *filename;
unsigned char otype;
SQLSMALLINT sqltype, ctype, scale;
SQLSMALLINT nullable;
SQLULEN precision;
odbc_result *result;
int numArgs, ... | 77,228,738,256,563,890,000,000,000,000,000,000,000 | php_odbc.c | 277,987,255,287,351,450,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2006-7243 | PHP before 5.3.4 accepts the \0 character in a pathname, which might allow context-dependent attackers to bypass intended access restrictions by placing a safe file extension after this character, as demonstrated by .php\0.jpg at the end of the argument to the file_exists function. | https://nvd.nist.gov/vuln/detail/CVE-2006-7243 |
208,490 | amanda | 2ba9a5fb84ba2faaeb95695a03bd7f26cbdfedb8 | https://github.com/zmanda/amanda | https://github.com/zmanda/amanda/commit/2ba9a5fb84ba2faaeb95695a03bd7f26cbdfedb8 | * client-src/runtar.c: Filter tar arguments
* installcheck/runtar.pl: Check runtar errorr
* installcheck/Makefile.am: Add runtar.pl
git-svn-id: https://svn.code.sf.net/p/amanda/code/amanda/trunk@6479 a8d146d6-cc15-0410-8900-af154a0219e0 | 1 | main(
int argc,
char ** argv)
{
#ifdef GNUTAR
int i;
char *e;
char *dbf;
char *cmdline;
GPtrArray *array = g_ptr_array_new();
gchar **strings;
char **new_argv;
char **env;
#endif
if (argc > 1 && argv[1] && g_str_equal(argv[1], "--version")) {
printf("runtar-%s\n", VERSION)... | 121,373,800,632,588,590,000,000,000,000,000,000,000 | None | null | [
"CWE-77"
] | CVE-2016-10729 | An issue was discovered in Amanda 3.3.1. A user with backup privileges can trivially compromise a client installation. The "runtar" setuid root binary does not check for additional arguments supplied after --create, allowing users to manipulate commands and perform command injection as root. | https://nvd.nist.gov/vuln/detail/CVE-2016-10729 |
411,803 | amanda | 2ba9a5fb84ba2faaeb95695a03bd7f26cbdfedb8 | https://github.com/zmanda/amanda | https://github.com/zmanda/amanda/commit/2ba9a5fb84ba2faaeb95695a03bd7f26cbdfedb8 | * client-src/runtar.c: Filter tar arguments
* installcheck/runtar.pl: Check runtar errorr
* installcheck/Makefile.am: Add runtar.pl
git-svn-id: https://svn.code.sf.net/p/amanda/code/amanda/trunk@6479 a8d146d6-cc15-0410-8900-af154a0219e0 | 0 | main(
int argc,
char ** argv)
{
#ifdef GNUTAR
int i;
char *e;
char *dbf;
char *cmdline;
GPtrArray *array = g_ptr_array_new();
gchar **strings;
char **new_argv;
char **env;
#endif
int good_option;
if (argc > 1 && argv[1] && g_str_equal(argv[1], "--version")) {
printf("r... | 63,839,399,915,262,820,000,000,000,000,000,000,000 | None | null | [
"CWE-77"
] | CVE-2016-10729 | An issue was discovered in Amanda 3.3.1. A user with backup privileges can trivially compromise a client installation. The "runtar" setuid root binary does not check for additional arguments supplied after --create, allowing users to manipulate commands and perform command injection as root. | https://nvd.nist.gov/vuln/detail/CVE-2016-10729 |
208,491 | qemu | 5e796671e6b8d5de4b0b423dce1b3eba144a92c9 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/5e796671e6b8d5de4b0b423dce1b3eba144a92c9 | usbredir: fix free call
data might point into the middle of a larger buffer, there is a separate
free_on_destroy pointer passed into bufp_alloc() to handle that. It is
only used in the normal workflow though, not when dropping packets due
to the queue being full. Fix that.
Resolves: https://gitlab.com/qemu-project/... | 1 | static int bufp_alloc(USBRedirDevice *dev, uint8_t *data, uint16_t len,
uint8_t status, uint8_t ep, void *free_on_destroy)
{
struct buf_packet *bufp;
if (!dev->endpoint[EP2I(ep)].bufpq_dropping_packets &&
dev->endpoint[EP2I(ep)].bufpq_size >
2 * dev->endpoint[EP2I(ep)].bufpq_target_size... | 217,526,934,536,260,350,000,000,000,000,000,000,000 | redirect.c | 122,117,011,284,903,550,000,000,000,000,000,000,000 | [
"CWE-763"
] | CVE-2021-3682 | A flaw was found in the USB redirector device emulation of QEMU in versions prior to 6.1.0-rc2. It occurs when dropping packets during a bulk transfer from a SPICE client due to the packet queue being full. A malicious SPICE client could use this flaw to make QEMU call free() with faked heap chunk metadata, resulting i... | https://nvd.nist.gov/vuln/detail/CVE-2021-3682 |
411,804 | qemu | 5e796671e6b8d5de4b0b423dce1b3eba144a92c9 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/5e796671e6b8d5de4b0b423dce1b3eba144a92c9 | usbredir: fix free call
data might point into the middle of a larger buffer, there is a separate
free_on_destroy pointer passed into bufp_alloc() to handle that. It is
only used in the normal workflow though, not when dropping packets due
to the queue being full. Fix that.
Resolves: https://gitlab.com/qemu-project/... | 0 | static int bufp_alloc(USBRedirDevice *dev, uint8_t *data, uint16_t len,
uint8_t status, uint8_t ep, void *free_on_destroy)
{
struct buf_packet *bufp;
if (!dev->endpoint[EP2I(ep)].bufpq_dropping_packets &&
dev->endpoint[EP2I(ep)].bufpq_size >
2 * dev->endpoint[EP2I(ep)].bufpq_target_size... | 277,052,429,112,878,600,000,000,000,000,000,000,000 | redirect.c | 234,780,020,806,162,370,000,000,000,000,000,000,000 | [
"CWE-763"
] | CVE-2021-3682 | A flaw was found in the USB redirector device emulation of QEMU in versions prior to 6.1.0-rc2. It occurs when dropping packets during a bulk transfer from a SPICE client due to the packet queue being full. A malicious SPICE client could use this flaw to make QEMU call free() with faked heap chunk metadata, resulting i... | https://nvd.nist.gov/vuln/detail/CVE-2021-3682 |
208,507 | liblouis | d4fc803687e38a5355fb686bf98cc082951f3043 | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/d4fc803687e38a5355fb686bf98cc082951f3043 | Use a standard buffer size for translating
I believe this fixes #591 (the second part of of it) | 1 | translate_input(int forward_translation, char *table_name) {
char charbuf[BUFSIZE];
uint8_t *outputbuf;
size_t outlen;
widechar inbuf[BUFSIZE];
widechar transbuf[BUFSIZE];
int inlen;
int translen;
int k;
int ch = 0;
int result;
while (1) {
translen = BUFSIZE;
k = 0;
while ((ch = fgetc(input)) != '\n' &... | 48,398,905,462,724,660,000,000,000,000,000,000,000 | lou_translate.c | 185,814,593,716,900,830,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-11683 | Liblouis 3.5.0 has a stack-based Buffer Overflow in the function parseChars in compileTranslationTable.c, a different vulnerability than CVE-2018-11440. | https://nvd.nist.gov/vuln/detail/CVE-2018-11683 |
411,945 | liblouis | d4fc803687e38a5355fb686bf98cc082951f3043 | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/d4fc803687e38a5355fb686bf98cc082951f3043 | Use a standard buffer size for translating
I believe this fixes #591 (the second part of of it) | 0 | translate_input(int forward_translation, char *table_name) {
char charbuf[MAXSTRING];
uint8_t *outputbuf;
size_t outlen;
widechar inbuf[MAXSTRING];
widechar transbuf[MAXSTRING];
int inlen;
int translen;
int k;
int ch = 0;
int result;
while (1) {
translen = MAXSTRING;
k = 0;
while ((ch = fgetc(input)) !... | 286,137,544,674,972,640,000,000,000,000,000,000,000 | lou_translate.c | 339,960,829,354,774,300,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-11683 | Liblouis 3.5.0 has a stack-based Buffer Overflow in the function parseChars in compileTranslationTable.c, a different vulnerability than CVE-2018-11440. | https://nvd.nist.gov/vuln/detail/CVE-2018-11683 |
208,512 | wkhtmltopdf | 2a5f25077895fb075812c0f599326f079a59d6cf | https://github.com/wkhtmltopdf/wkhtmltopdf | https://github.com/wkhtmltopdf/wkhtmltopdf/commit/2a5f25077895fb075812c0f599326f079a59d6cf | BREAKING CHANGE: block local filesystem access by default
fixes #4536 | 1 | LoadPage::LoadPage():
jsdelay(200),
windowStatus(""),
zoomFactor(1.0),
repeatCustomHeaders(false),
blockLocalFileAccess(false),
stopSlowScripts(true),
debugJavascript(false),
loadErrorHandling(abort),
mediaLoadErrorHandling(ignore),
cacheDir(""),
proxyHostNameLookup(false) {}; | 104,272,406,081,399,020,000,000,000,000,000,000,000 | loadsettings.cc | 200,230,048,762,050,950,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2020-21365 | Directory traversal vulnerability in wkhtmltopdf through 0.12.5 allows remote attackers to read local files and disclose sensitive information via a crafted html file running with the default configurations. | https://nvd.nist.gov/vuln/detail/CVE-2020-21365 |
411,983 | wkhtmltopdf | 2a5f25077895fb075812c0f599326f079a59d6cf | https://github.com/wkhtmltopdf/wkhtmltopdf | https://github.com/wkhtmltopdf/wkhtmltopdf/commit/2a5f25077895fb075812c0f599326f079a59d6cf | BREAKING CHANGE: block local filesystem access by default
fixes #4536 | 0 | LoadPage::LoadPage():
jsdelay(200),
windowStatus(""),
zoomFactor(1.0),
repeatCustomHeaders(false),
blockLocalFileAccess(true),
stopSlowScripts(true),
debugJavascript(false),
loadErrorHandling(abort),
mediaLoadErrorHandling(ignore),
cacheDir(""),
proxyHostNameLookup(false) {}; | 306,659,183,970,725,670,000,000,000,000,000,000,000 | loadsettings.cc | 195,271,432,656,056,180,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2020-21365 | Directory traversal vulnerability in wkhtmltopdf through 0.12.5 allows remote attackers to read local files and disclose sensitive information via a crafted html file running with the default configurations. | https://nvd.nist.gov/vuln/detail/CVE-2020-21365 |
208,513 | ImageMagick | c0fe488e7052f68d4eb7768805a857ef6fef928d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c0fe488e7052f68d4eb7768805a857ef6fef928d | https://github.com/ImageMagick/ImageMagick/issues/1520 | 1 | static Image *ReadPCLImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define CropBox "CropBox"
#define DeviceCMYK "DeviceCMYK"
#define MediaBox "MediaBox"
#define RenderPCLText " Rendering PCL... "
char
command[MagickPathExtent],
*density,
filename[MagickPathExtent],
geometry[Magi... | 119,131,715,192,438,950,000,000,000,000,000,000,000 | pcl.c | 211,547,946,804,995,500,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-12976 | ImageMagick 7.0.8-34 has a memory leak in the ReadPCLImage function in coders/pcl.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12976 |
411,984 | ImageMagick | c0fe488e7052f68d4eb7768805a857ef6fef928d | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/c0fe488e7052f68d4eb7768805a857ef6fef928d | https://github.com/ImageMagick/ImageMagick/issues/1520 | 0 | static Image *ReadPCLImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
#define CropBox "CropBox"
#define DeviceCMYK "DeviceCMYK"
#define MediaBox "MediaBox"
#define RenderPCLText " Rendering PCL... "
char
command[MagickPathExtent],
*density,
filename[MagickPathExtent],
geometry[Magi... | 119,738,671,382,200,980,000,000,000,000,000,000,000 | pcl.c | 77,692,958,060,119,370,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-12976 | ImageMagick 7.0.8-34 has a memory leak in the ReadPCLImage function in coders/pcl.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-12976 |
208,516 | php-src | a6fdc5bb27b20d889de0cd29318b3968aabb57bd | https://github.com/php/php-src | https://git.php.net/?p=php-src.git;a=commit;h=a6fdc5bb27b20d889de0cd29318b3968aabb57bd | Fix bug #71498: Out-of-Bound Read in phar_parse_zipfile() | 1 | int phar_parse_zipfile(php_stream *fp, char *fname, int fname_len, char *alias, int alias_len, phar_archive_data** pphar, char **error TSRMLS_DC) /* {{{ */
{
phar_zip_dir_end locator;
char buf[sizeof(locator) + 65536];
long size;
php_uint16 i;
phar_archive_data *mydata = NULL;
phar_entry_info entry = {0};
char *... | 144,448,204,992,415,250,000,000,000,000,000,000,000 | zip.c | 235,238,176,058,153,530,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-3142 | The phar_parse_zipfile function in zip.c in the PHAR extension in PHP before 5.5.33 and 5.6.x before 5.6.19 allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read and application crash) by placing a PK\x05\x06 signature at an invalid location. | https://nvd.nist.gov/vuln/detail/CVE-2016-3142 |
412,055 | php-src | a6fdc5bb27b20d889de0cd29318b3968aabb57bd | https://github.com/php/php-src | https://git.php.net/?p=php-src.git;a=commit;h=a6fdc5bb27b20d889de0cd29318b3968aabb57bd | Fix bug #71498: Out-of-Bound Read in phar_parse_zipfile() | 0 | int phar_parse_zipfile(php_stream *fp, char *fname, int fname_len, char *alias, int alias_len, phar_archive_data** pphar, char **error TSRMLS_DC) /* {{{ */
{
phar_zip_dir_end locator;
char buf[sizeof(locator) + 65536];
long size;
php_uint16 i;
phar_archive_data *mydata = NULL;
phar_entry_info entry = {0};
char *... | 62,888,802,600,100,890,000,000,000,000,000,000,000 | zip.c | 137,968,341,018,962,300,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-3142 | The phar_parse_zipfile function in zip.c in the PHAR extension in PHP before 5.5.33 and 5.6.x before 5.6.19 allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read and application crash) by placing a PK\x05\x06 signature at an invalid location. | https://nvd.nist.gov/vuln/detail/CVE-2016-3142 |
208,519 | gnutls | c5aaa488a3d6df712dc8dff23a049133cab5ec1b | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/c5aaa488a3d6df712dc8dff23a049133cab5ec1b | gnutls_x509_ext_import_proxy: fix issue reading the policy language
If the language was set but the policy wasn't, that could lead to
a double free, as the value returned to the user was freed. | 1 | int gnutls_x509_ext_import_proxy(const gnutls_datum_t * ext, int *pathlen,
char **policyLanguage, char **policy,
size_t * sizeof_policy)
{
ASN1_TYPE c2 = ASN1_TYPE_EMPTY;
int result;
gnutls_datum_t value = { NULL, 0 };
if ((result = asn1_create_element
(_gnutls_get_pkix(), "PKIX1.ProxyCertI... | 94,257,636,872,994,820,000,000,000,000,000,000,000 | x509_ext.c | 206,488,673,205,450,580,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-5334 | Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attackers to have unspecified impact via crafted policy language information in an X.509 certificate with a Proxy Certificate Information extension. | https://nvd.nist.gov/vuln/detail/CVE-2017-5334 |
412,068 | gnutls | c5aaa488a3d6df712dc8dff23a049133cab5ec1b | http://git.savannah.gnu.org/cgit/gnutls | https://gitlab.com/gnutls/gnutls/commit/c5aaa488a3d6df712dc8dff23a049133cab5ec1b | gnutls_x509_ext_import_proxy: fix issue reading the policy language
If the language was set but the policy wasn't, that could lead to
a double free, as the value returned to the user was freed. | 0 | int gnutls_x509_ext_import_proxy(const gnutls_datum_t * ext, int *pathlen,
char **policyLanguage, char **policy,
size_t * sizeof_policy)
{
ASN1_TYPE c2 = ASN1_TYPE_EMPTY;
int result;
gnutls_datum_t value1 = { NULL, 0 };
gnutls_datum_t value2 = { NULL, 0 };
if ((result = asn1_create_element
... | 158,853,549,467,112,000,000,000,000,000,000,000,000 | x509_ext.c | 326,214,344,446,615,780,000,000,000,000,000,000,000 | [
"CWE-415"
] | CVE-2017-5334 | Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attackers to have unspecified impact via crafted policy language information in an X.509 certificate with a Proxy Certificate Information extension. | https://nvd.nist.gov/vuln/detail/CVE-2017-5334 |
208,527 | libffi | 44a6c28545186d78642487927952844156fc7ab5 | https://github.com/libffi/libffi | https://github.com/libffi/libffi/commit/44a6c28545186d78642487927952844156fc7ab5 | aarch64: Flush code mapping in addition to data mapping (#471)
This needs a new function, ffi_data_to_code_pointer, to translate
from data pointers to code pointers.
Fixes issue #470. | 1 | ffi_prep_closure_loc (ffi_closure *closure,
ffi_cif* cif,
void (*fun)(ffi_cif*,void*,void**,void*),
void *user_data,
void *codeloc)
{
if (cif->abi != FFI_SYSV)
return FFI_BAD_ABI;
void (*start)(void);
if (cif->flags & ... | 15,461,843,385,628,788,000,000,000,000,000,000,000 | ffi.c | 102,492,329,377,864,080,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-9391 | An issue was discovered in the Linux kernel 5.4 and 5.5 through 5.5.6 on the AArch64 architecture. It ignores the top byte in the address passed to the brk system call, potentially moving the memory break downwards when the application expects it to move upwards, aka CID-dcde237319e6. This has been observed to cause he... | https://nvd.nist.gov/vuln/detail/CVE-2020-9391 |
412,201 | libffi | 44a6c28545186d78642487927952844156fc7ab5 | https://github.com/libffi/libffi | https://github.com/libffi/libffi/commit/44a6c28545186d78642487927952844156fc7ab5 | aarch64: Flush code mapping in addition to data mapping (#471)
This needs a new function, ffi_data_to_code_pointer, to translate
from data pointers to code pointers.
Fixes issue #470. | 0 | ffi_prep_closure_loc (ffi_closure *closure,
ffi_cif* cif,
void (*fun)(ffi_cif*,void*,void**,void*),
void *user_data,
void *codeloc)
{
if (cif->abi != FFI_SYSV)
return FFI_BAD_ABI;
void (*start)(void);
if (cif->flags & ... | 307,771,365,670,093,600,000,000,000,000,000,000,000 | ffi.c | 335,563,715,378,162,570,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-9391 | An issue was discovered in the Linux kernel 5.4 and 5.5 through 5.5.6 on the AArch64 architecture. It ignores the top byte in the address passed to the brk system call, potentially moving the memory break downwards when the application expects it to move upwards, aka CID-dcde237319e6. This has been observed to cause he... | https://nvd.nist.gov/vuln/detail/CVE-2020-9391 |
208,529 | snapd | bdbfeebef03245176ae0dc323392bb0522a339b1 | https://github.com/snapcore/snapd | https://github.com/snapcore/snapd/commit/bdbfeebef03245176ae0dc323392bb0522a339b1 | cmd/snap-confine: chown private /tmp parent to root.root
When snap-confine creates a private /tmp directory for a given snap it
first creates a temporary directory in /tmp/ named after the snap, along
with a random name. Inside that directory it creates a /tmp directory
with permissions appropriate for a future /tmp, ... | 1 | static void setup_private_mount(const char *snap_name)
{
uid_t uid = getuid();
gid_t gid = getgid();
char tmpdir[MAX_BUF] = { 0 };
// Create a 0700 base directory, this is the base dir that is
// protected from other users.
//
// Under that basedir, we put a 1777 /tmp dir that is then bind
// mounted for the a... | 257,560,557,893,467,850,000,000,000,000,000,000,000 | mount-support.c | 246,567,729,900,845,820,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-11502 | snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user. Consequently, that user had unintended access to a private /tmp directory. | https://nvd.nist.gov/vuln/detail/CVE-2019-11502 |
412,293 | snapd | bdbfeebef03245176ae0dc323392bb0522a339b1 | https://github.com/snapcore/snapd | https://github.com/snapcore/snapd/commit/bdbfeebef03245176ae0dc323392bb0522a339b1 | cmd/snap-confine: chown private /tmp parent to root.root
When snap-confine creates a private /tmp directory for a given snap it
first creates a temporary directory in /tmp/ named after the snap, along
with a random name. Inside that directory it creates a /tmp directory
with permissions appropriate for a future /tmp, ... | 0 | static void setup_private_mount(const char *snap_name)
{
char tmpdir[MAX_BUF] = { 0 };
// Create a 0700 base directory, this is the base dir that is
// protected from other users.
//
// Under that basedir, we put a 1777 /tmp dir that is then bind
// mounted for the applications to use
sc_must_snprintf(tmpdir, s... | 204,424,472,674,232,730,000,000,000,000,000,000,000 | mount-support.c | 3,047,395,040,171,936,700,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-11502 | snap-confine in snapd before 2.38 incorrectly set the ownership of a snap application to the uid and gid of the first calling user. Consequently, that user had unintended access to a private /tmp directory. | https://nvd.nist.gov/vuln/detail/CVE-2019-11502 |
208,531 | torque | f2f4c950f3d461a249111c8826da3beaafccace9 | https://github.com/adaptivecomputing/torque | https://github.com/adaptivecomputing/torque/commit/f2f4c950f3d461a249111c8826da3beaafccace9 | TRQ-2885 - limit tm_adopt() to only adopt a session id that
is owned by the calling user. | 1 | int tm_adopt(
char *id,
int adoptCmd,
pid_t pid)
{
int rc = TM_SUCCESS;
int status, ret;
pid_t sid;
char *env;
struct tcp_chan *chan = NULL;
sid = getsid(pid);
/* Must be the only call to call to tm and
must only be called once */
if (init_done) return TM_BADINIT;
init_done... | 65,514,663,756,065,650,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2014-3684 | The tm_adopt function in lib/Libifl/tm.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 5.0.x, 4.5.x, 4.2.x, and earlier does not validate that the owner of the process also owns the adopted session id, which allows remote authenticated users to kill arbitrary processes via a crafted ... | https://nvd.nist.gov/vuln/detail/CVE-2014-3684 |
412,305 | torque | f2f4c950f3d461a249111c8826da3beaafccace9 | https://github.com/adaptivecomputing/torque | https://github.com/adaptivecomputing/torque/commit/f2f4c950f3d461a249111c8826da3beaafccace9 | TRQ-2885 - limit tm_adopt() to only adopt a session id that
is owned by the calling user. | 0 | int tm_adopt(
char *id,
int adoptCmd,
pid_t pid)
{
int rc = TM_SUCCESS;
int status, ret;
pid_t sid;
char *env;
struct tcp_chan *chan = NULL;
sid = getsid(pid);
/* do not adopt a sid not owned by caller */
if (!ispidowner(sid))
return(TM_EPERM);
/* Must be the only call to cal... | 307,094,664,551,941,400,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2014-3684 | The tm_adopt function in lib/Libifl/tm.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 5.0.x, 4.5.x, 4.2.x, and earlier does not validate that the owner of the process also owns the adopted session id, which allows remote authenticated users to kill arbitrary processes via a crafted ... | https://nvd.nist.gov/vuln/detail/CVE-2014-3684 |
208,534 | resiprocate | d67a9ca6fd06ca65d23e313bdbad1ef4dd3aa0df | https://github.com/resiprocate/resiprocate | https://github.com/resiprocate/resiprocate/commit/d67a9ca6fd06ca65d23e313bdbad1ef4dd3aa0df | ares: Prevent buffer overlow in ares_parse_a_reply (CVE-2017-9454)
This buffer overflow is in the embedded copy of ares that will be
used unless the external alternative c-ares is used by specifying
the configure argument --with-c-ares.
It has been found with LibFuzzer from the LLVM project. | 1 | int ares_parse_a_reply(const unsigned char *abuf, int alen,
struct hostent **host)
{
unsigned int qdcount, ancount;
int status, i, rr_type, rr_class, rr_len, naddrs;
long int len;
int naliases;
const unsigned char *aptr;
char *hostname, *rr_name, *rr_data, **aliases;
struct in_addr *addrs;
stru... | 339,462,409,582,323,600,000,000,000,000,000,000,000 | ares_parse_a_reply.c | 202,110,915,441,919,850,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-9454 | Buffer overflow in the ares_parse_a_reply function in the embedded ares library in ReSIProcate before 1.12.0 allows remote attackers to cause a denial of service (out-of-bounds-read) via a crafted DNS response. | https://nvd.nist.gov/vuln/detail/CVE-2017-9454 |
412,328 | resiprocate | d67a9ca6fd06ca65d23e313bdbad1ef4dd3aa0df | https://github.com/resiprocate/resiprocate | https://github.com/resiprocate/resiprocate/commit/d67a9ca6fd06ca65d23e313bdbad1ef4dd3aa0df | ares: Prevent buffer overlow in ares_parse_a_reply (CVE-2017-9454)
This buffer overflow is in the embedded copy of ares that will be
used unless the external alternative c-ares is used by specifying
the configure argument --with-c-ares.
It has been found with LibFuzzer from the LLVM project. | 0 | int ares_parse_a_reply(const unsigned char *abuf, int alen,
struct hostent **host)
{
unsigned int qdcount, ancount;
int status, i, rr_type, rr_class, rr_len, naddrs;
long int len;
int naliases;
const unsigned char *aptr;
char *hostname, *rr_name, *rr_data, **aliases;
struct in_addr *addrs;
stru... | 191,536,719,324,548,300,000,000,000,000,000,000,000 | ares_parse_a_reply.c | 20,990,464,461,145,040,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2017-9454 | Buffer overflow in the ares_parse_a_reply function in the embedded ares library in ReSIProcate before 1.12.0 allows remote attackers to cause a denial of service (out-of-bounds-read) via a crafted DNS response. | https://nvd.nist.gov/vuln/detail/CVE-2017-9454 |
208,539 | linux | b91ee4aa2a2199ba4d4650706c272985a5a32d80 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b91ee4aa2a2199ba4d4650706c272985a5a32d80 | mISDN: enforce CAP_NET_RAW for raw sockets
When creating a raw AF_ISDN socket, CAP_NET_RAW needs to be checked
first.
Signed-off-by: Ori Nimron <orinimron123@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | base_sock_create(struct net *net, struct socket *sock, int protocol, int kern)
{
struct sock *sk;
if (sock->type != SOCK_RAW)
return -ESOCKTNOSUPPORT;
sk = sk_alloc(net, PF_ISDN, GFP_KERNEL, &mISDN_proto, kern);
if (!sk)
return -ENOMEM;
sock_init_data(sock, sk);
sock->ops = &base_sock_ops;
sock->state = S... | 181,360,018,897,903,400,000,000,000,000,000,000,000 | socket.c | 210,161,696,899,394,700,000,000,000,000,000,000,000 | [
"CWE-862"
] | CVE-2019-17055 | base_sock_create in drivers/isdn/mISDN/socket.c in the AF_ISDN network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-b91ee4aa2a21. | https://nvd.nist.gov/vuln/detail/CVE-2019-17055 |
412,365 | linux | b91ee4aa2a2199ba4d4650706c272985a5a32d80 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b91ee4aa2a2199ba4d4650706c272985a5a32d80 | mISDN: enforce CAP_NET_RAW for raw sockets
When creating a raw AF_ISDN socket, CAP_NET_RAW needs to be checked
first.
Signed-off-by: Ori Nimron <orinimron123@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net> | 0 | data_sock_create(struct net *net, struct socket *sock, int protocol, int kern)
{
struct sock *sk;
if (sock->type != SOCK_DGRAM)
return -ESOCKTNOSUPPORT;
sk = sk_alloc(net, PF_ISDN, GFP_KERNEL, &mISDN_proto, kern);
if (!sk)
return -ENOMEM;
sock_init_data(sock, sk);
sock->ops = &data_sock_ops;
sock->state ... | 279,231,744,026,003,660,000,000,000,000,000,000,000 | socket.c | 190,511,514,120,774,600,000,000,000,000,000,000,000 | [
"CWE-862"
] | CVE-2019-17055 | base_sock_create in drivers/isdn/mISDN/socket.c in the AF_ISDN network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-b91ee4aa2a21. | https://nvd.nist.gov/vuln/detail/CVE-2019-17055 |
208,545 | ghostpdl | bf72f1a3dd5392ee8291e3b1518a0c2c5dc6ba39 | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=bf72f1a3dd5392ee8291e3b1518a0c2c5dc6ba39 | Fix valgrind problems with gdevbjca.c
2 problems here. Firstly, we could access off the end of a row
while looking for runs. Change the indexing to fix this.
Secondly, we could overrun our gamma tables due to unexpectedly
large values. Add some clamping. | 1 | FloydSteinbergDitheringC(gx_device_bjc_printer *dev,
byte *row, byte *dithered, uint width,
uint raster, bool limit_extr, bool composeK)
{ byte byteC=0, byteM=0, byteY=0, byteK=0, bitmask = 0x80; /* first bit */
int i;
int errorC = 0, errorM = 0, errorY = 0, d... | 163,387,335,865,075,920,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2020-16297 | A buffer overflow vulnerability in FloydSteinbergDitheringC() in contrib/gdevbjca.c of Artifex Software GhostScript v9.50 allows a remote attacker to cause a denial of service via a crafted PDF file. This is fixed in v9.51. | https://nvd.nist.gov/vuln/detail/CVE-2020-16297 |
412,590 | ghostpdl | bf72f1a3dd5392ee8291e3b1518a0c2c5dc6ba39 | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=bf72f1a3dd5392ee8291e3b1518a0c2c5dc6ba39 | Fix valgrind problems with gdevbjca.c
2 problems here. Firstly, we could access off the end of a row
while looking for runs. Change the indexing to fix this.
Secondly, we could overrun our gamma tables due to unexpectedly
large values. Add some clamping. | 0 | FloydSteinbergDitheringC(gx_device_bjc_printer *dev,
byte *row, byte *dithered, uint width,
uint raster, bool limit_extr, bool composeK)
{ byte byteC=0, byteM=0, byteY=0, byteK=0, bitmask = 0x80; /* first bit */
int i;
int errorC = 0, errorM = 0, errorY = 0, d... | 632,914,042,391,170,200,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2020-16297 | A buffer overflow vulnerability in FloydSteinbergDitheringC() in contrib/gdevbjca.c of Artifex Software GhostScript v9.50 allows a remote attacker to cause a denial of service via a crafted PDF file. This is fixed in v9.51. | https://nvd.nist.gov/vuln/detail/CVE-2020-16297 |
208,552 | ImageMagick | 34a6a5a45e83a4af852090b4e43f168a380df979 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/34a6a5a45e83a4af852090b4e43f168a380df979 | https://github.com/ImageMagick/ImageMagick/issues/1523 | 1 | static MagickBooleanType WritePSImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
#define WriteRunlengthPacket(image,pixel,length,p) \
{ \
if ((image->alpha_trait != UndefinedPixelTrait) && (length != 0) && \
(GetPixelAlpha(image,p) == (Quantum) TransparentAlpha)) \
{ \
q=P... | 334,027,533,115,072,600,000,000,000,000,000,000,000 | ps.c | 96,341,791,813,690,300,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-9956 | In ImageMagick 7.0.8-35 Q16, there is a stack-based buffer overflow in the function PopHexPixel of coders/ps.c, which allows an attacker to cause a denial of service or code execution via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-9956 |
412,699 | ImageMagick | 34a6a5a45e83a4af852090b4e43f168a380df979 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/34a6a5a45e83a4af852090b4e43f168a380df979 | https://github.com/ImageMagick/ImageMagick/issues/1523 | 0 | static MagickBooleanType WritePSImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
#define WriteRunlengthPacket(image,pixel,length,p) \
{ \
if ((image->alpha_trait != UndefinedPixelTrait) && (length != 0) && \
(GetPixelAlpha(image,p) == (Quantum) TransparentAlpha)) \
{ \
q=P... | 79,953,295,311,571,450,000,000,000,000,000,000,000 | ps.c | 177,420,798,447,153,000,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-9956 | In ImageMagick 7.0.8-35 Q16, there is a stack-based buffer overflow in the function PopHexPixel of coders/ps.c, which allows an attacker to cause a denial of service or code execution via a crafted image file. | https://nvd.nist.gov/vuln/detail/CVE-2019-9956 |
208,553 | php-src | 0bfb970f43acd1e81d11be1154805f86655f15d5 | https://github.com/php/php-src | https://github.com/php/php-src/commit/0bfb970f43acd1e81d11be1154805f86655f15d5?w=1 | Fix bug #72928 - Out of bound when verify signature of zip phar in phar_parse_zipfile
(cherry picked from commit 19484ab77466f99c78fc0e677f7e03da0584d6a2) | 1 | int phar_parse_zipfile(php_stream *fp, char *fname, int fname_len, char *alias, int alias_len, phar_archive_data** pphar, char **error) /* {{{ */
{
phar_zip_dir_end locator;
char buf[sizeof(locator) + 65536];
zend_long size;
php_uint16 i;
phar_archive_data *mydata = NULL;
phar_entry_info entry = {0};
char *p = b... | 127,037,039,367,254,160,000,000,000,000,000,000,000 | zip.c | 257,773,826,683,404,360,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7414 | The ZIP signature-verification feature in PHP before 5.6.26 and 7.x before 7.0.11 does not ensure that the uncompressed_filesize field is large enough, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via a crafted PHAR archive, related t... | https://nvd.nist.gov/vuln/detail/CVE-2016-7414 |
412,728 | php-src | 0bfb970f43acd1e81d11be1154805f86655f15d5 | https://github.com/php/php-src | https://github.com/php/php-src/commit/0bfb970f43acd1e81d11be1154805f86655f15d5?w=1 | Fix bug #72928 - Out of bound when verify signature of zip phar in phar_parse_zipfile
(cherry picked from commit 19484ab77466f99c78fc0e677f7e03da0584d6a2) | 0 | int phar_parse_zipfile(php_stream *fp, char *fname, int fname_len, char *alias, int alias_len, phar_archive_data** pphar, char **error) /* {{{ */
{
phar_zip_dir_end locator;
char buf[sizeof(locator) + 65536];
zend_long size;
php_uint16 i;
phar_archive_data *mydata = NULL;
phar_entry_info entry = {0};
char *p = b... | 26,612,929,532,876,310,000,000,000,000,000,000,000 | zip.c | 64,001,155,956,632,535,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7414 | The ZIP signature-verification feature in PHP before 5.6.26 and 7.x before 7.0.11 does not ensure that the uncompressed_filesize field is large enough, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via a crafted PHAR archive, related t... | https://nvd.nist.gov/vuln/detail/CVE-2016-7414 |
208,554 | php-src | 0bfb970f43acd1e81d11be1154805f86655f15d5 | https://github.com/php/php-src | https://github.com/php/php-src/commit/0bfb970f43acd1e81d11be1154805f86655f15d5?w=1 | Fix bug #72928 - Out of bound when verify signature of zip phar in phar_parse_zipfile
(cherry picked from commit 19484ab77466f99c78fc0e677f7e03da0584d6a2) | 1 | int phar_verify_signature(php_stream *fp, size_t end_of_phar, php_uint32 sig_type, char *sig, int sig_len, char *fname, char **signature, int *signature_len, char **error) /* {{{ */
{
int read_size, len;
zend_off_t read_len;
unsigned char buf[1024];
php_stream_rewind(fp);
switch (sig_type) {
case PHAR_SIG_OPEN... | 311,598,902,154,312,660,000,000,000,000,000,000,000 | util.c | 315,183,083,071,023,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7414 | The ZIP signature-verification feature in PHP before 5.6.26 and 7.x before 7.0.11 does not ensure that the uncompressed_filesize field is large enough, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via a crafted PHAR archive, related t... | https://nvd.nist.gov/vuln/detail/CVE-2016-7414 |
412,714 | php-src | 0bfb970f43acd1e81d11be1154805f86655f15d5 | https://github.com/php/php-src | https://github.com/php/php-src/commit/0bfb970f43acd1e81d11be1154805f86655f15d5?w=1 | Fix bug #72928 - Out of bound when verify signature of zip phar in phar_parse_zipfile
(cherry picked from commit 19484ab77466f99c78fc0e677f7e03da0584d6a2) | 0 | int phar_verify_signature(php_stream *fp, size_t end_of_phar, php_uint32 sig_type, char *sig, int sig_len, char *fname, char **signature, int *signature_len, char **error) /* {{{ */
{
int read_size, len;
zend_off_t read_len;
unsigned char buf[1024];
php_stream_rewind(fp);
switch (sig_type) {
case PHAR_SIG_OPEN... | 312,219,676,042,754,280,000,000,000,000,000,000,000 | util.c | 279,735,235,878,173,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-7414 | The ZIP signature-verification feature in PHP before 5.6.26 and 7.x before 7.0.11 does not ensure that the uncompressed_filesize field is large enough, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via a crafted PHAR archive, related t... | https://nvd.nist.gov/vuln/detail/CVE-2016-7414 |
208,555 | curl | 9b5e12a5491d2e6b68e0c88ca56f3a9ef9fba400 | https://github.com/curl/curl | https://github.com/curl/curl/commit/9b5e12a5491d2e6b68e0c88ca56f3a9ef9fba400 | url: fix alignment of ssl_backend_data struct
- Align the array of ssl_backend_data on a max 32 byte boundary.
8 is likely to be ok but I went with 32 for posterity should one of
the ssl_backend_data structs change to contain a larger sized variable
in the future.
Prior to this change (since dev 70f1db3, release 7.5... | 1 | static struct connectdata *allocate_conn(struct Curl_easy *data)
{
#ifdef USE_SSL
#define SSL_EXTRA + 4 * Curl_ssl->sizeof_ssl_backend_data - sizeof(long long)
#else
#define SSL_EXTRA 0
#endif
struct connectdata *conn = calloc(1, sizeof(struct connectdata) + SSL_EXTRA);
if(!conn)
return NULL;
conn->handler =... | 112,760,880,146,197,920,000,000,000,000,000,000,000 | url.c | 27,542,268,772,603,316,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8818 | curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library. | https://nvd.nist.gov/vuln/detail/CVE-2017-8818 |
412,755 | curl | 9b5e12a5491d2e6b68e0c88ca56f3a9ef9fba400 | https://github.com/curl/curl | https://github.com/curl/curl/commit/9b5e12a5491d2e6b68e0c88ca56f3a9ef9fba400 | url: fix alignment of ssl_backend_data struct
- Align the array of ssl_backend_data on a max 32 byte boundary.
8 is likely to be ok but I went with 32 for posterity should one of
the ssl_backend_data structs change to contain a larger sized variable
in the future.
Prior to this change (since dev 70f1db3, release 7.5... | 0 | static struct connectdata *allocate_conn(struct Curl_easy *data)
{
struct connectdata *conn;
size_t connsize = sizeof(struct connectdata);
#ifdef USE_SSL
/* SSLBK_MAX_ALIGN: The max byte alignment a CPU would use */
#define SSLBK_MAX_ALIGN 32
/* The SSL backend-specific data (ssl_backend_data) objects are alloca... | 24,557,082,063,837,403,000,000,000,000,000,000,000 | url.c | 261,059,947,055,172,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2017-8818 | curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library. | https://nvd.nist.gov/vuln/detail/CVE-2017-8818 |
208,606 | ImageMagick | 6ae32a9038e360b3491969d5d03d490884f02b4c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6ae32a9038e360b3491969d5d03d490884f02b4c | https://github.com/ImageMagick/ImageMagick/issues/1562 | 1 | static MagickBooleanType WriteSGIImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
CompressionType
compression;
const char
*value;
MagickBooleanType
status;
MagickOffsetType
scene;
MagickSizeType
number_pixels;
MemoryInfo
*pixel_info;
SGIInfo
i... | 94,669,378,590,397,270,000,000,000,000,000,000,000 | sgi.c | 326,674,074,761,053,070,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19948 | In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer overflow in the function WriteSGIImage of coders/sgi.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19948 |
413,054 | ImageMagick | 6ae32a9038e360b3491969d5d03d490884f02b4c | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/6ae32a9038e360b3491969d5d03d490884f02b4c | https://github.com/ImageMagick/ImageMagick/issues/1562 | 0 | static MagickBooleanType WriteSGIImage(const ImageInfo *image_info,Image *image,
ExceptionInfo *exception)
{
CompressionType
compression;
const char
*value;
MagickBooleanType
status;
MagickOffsetType
scene;
MagickSizeType
number_pixels;
MemoryInfo
*pixel_info;
SGIInfo
i... | 88,790,099,270,894,850,000,000,000,000,000,000,000 | sgi.c | 267,865,120,780,747,700,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2019-19948 | In ImageMagick 7.0.8-43 Q16, there is a heap-based buffer overflow in the function WriteSGIImage of coders/sgi.c. | https://nvd.nist.gov/vuln/detail/CVE-2019-19948 |
208,641 | php-src | 08da7c73726f7b86b67d6f0ff87c73c585a7834a | https://github.com/php/php-src | https://github.com/php/php-src/commit/08da7c73726f7b86b67d6f0ff87c73c585a7834a | Fix #76449: SIGSEGV in firebird_handle_doer
We need to verify that the `result_size` is not larger than our buffer,
and also should make sure that the `len` which is passed to
`isc_vax_integer()` has a permissible value; otherwise we bail out. | 1 | static zend_long firebird_handle_doer(pdo_dbh_t *dbh, const char *sql, size_t sql_len) /* {{{ */
{
pdo_firebird_db_handle *H = (pdo_firebird_db_handle *)dbh->driver_data;
isc_stmt_handle stmt = PDO_FIREBIRD_HANDLE_INITIALIZER;
static char const info_count[] = { isc_info_sql_records };
char result[64];
int ret = 0;... | 255,731,076,067,573,970,000,000,000,000,000,000,000 | firebird_driver.c | 117,172,478,662,797,920,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-21704 | In PHP versions 7.3.x below 7.3.29, 7.4.x below 7.4.21 and 8.0.x below 8.0.8, when using Firebird PDO driver extension, a malicious database server could cause crashes in various database functions, such as getAttribute(), execute(), fetch() and others by returning invalid response data that is not parsed correctly by ... | https://nvd.nist.gov/vuln/detail/CVE-2021-21704 |
413,234 | php-src | 08da7c73726f7b86b67d6f0ff87c73c585a7834a | https://github.com/php/php-src | https://github.com/php/php-src/commit/08da7c73726f7b86b67d6f0ff87c73c585a7834a | Fix #76449: SIGSEGV in firebird_handle_doer
We need to verify that the `result_size` is not larger than our buffer,
and also should make sure that the `len` which is passed to
`isc_vax_integer()` has a permissible value; otherwise we bail out. | 0 | static zend_long firebird_handle_doer(pdo_dbh_t *dbh, const char *sql, size_t sql_len) /* {{{ */
{
pdo_firebird_db_handle *H = (pdo_firebird_db_handle *)dbh->driver_data;
isc_stmt_handle stmt = PDO_FIREBIRD_HANDLE_INITIALIZER;
static char const info_count[] = { isc_info_sql_records };
char result[64];
int ret = 0;... | 67,473,222,319,907,440,000,000,000,000,000,000,000 | firebird_driver.c | 151,766,053,958,939,870,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-21704 | In PHP versions 7.3.x below 7.3.29, 7.4.x below 7.4.21 and 8.0.x below 8.0.8, when using Firebird PDO driver extension, a malicious database server could cause crashes in various database functions, such as getAttribute(), execute(), fetch() and others by returning invalid response data that is not parsed correctly by ... | https://nvd.nist.gov/vuln/detail/CVE-2021-21704 |
208,642 | file | 956a45ab1c54b11304b367056f41905e72a02380 | https://github.com/file/file | https://github.com/file/file/commit/956a45ab1c54b11304b367056f41905e72a02380#diff-bc5c24ef9f39a5f4963ca28ecbc645b3L423 | support ld build id printing. | 1 | donote(struct magic_set *ms, void *vbuf, size_t offset, size_t size,
int clazz, int swap, size_t align, int *flags)
{
Elf32_Nhdr nh32;
Elf64_Nhdr nh64;
size_t noff, doff;
#ifdef ELFCORE
int os_style = -1;
#endif
uint32_t namesz, descsz;
unsigned char *nbuf = CAST(unsigned char *, vbuf);
(void)memcpy(xnh_add... | 297,200,084,306,026,730,000,000,000,000,000,000,000 | readelf.c | 311,516,117,972,153,830,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9620 | The ELF parser in file 5.08 through 5.21 allows remote attackers to cause a denial of service via a large number of notes. | https://nvd.nist.gov/vuln/detail/CVE-2014-9620 |
413,244 | file | 956a45ab1c54b11304b367056f41905e72a02380 | https://github.com/file/file | https://github.com/file/file/commit/956a45ab1c54b11304b367056f41905e72a02380#diff-bc5c24ef9f39a5f4963ca28ecbc645b3L423 | support ld build id printing. | 0 | donote(struct magic_set *ms, void *vbuf, size_t offset, size_t size,
int clazz, int swap, size_t align, int *flags)
{
Elf32_Nhdr nh32;
Elf64_Nhdr nh64;
size_t noff, doff;
#ifdef ELFCORE
int os_style = -1;
#endif
uint32_t namesz, descsz;
unsigned char *nbuf = CAST(unsigned char *, vbuf);
(void)memcpy(xnh_add... | 118,818,769,651,638,040,000,000,000,000,000,000,000 | readelf.c | 5,752,367,705,290,284,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2014-9620 | The ELF parser in file 5.08 through 5.21 allows remote attackers to cause a denial of service via a large number of notes. | https://nvd.nist.gov/vuln/detail/CVE-2014-9620 |
208,643 | cryptsetup | 52f5cb8cedf22fb3e14c744814ec8af7614146c7 | https://gitlab.com/cryptsetup/cryptsetup | https://gitlab.com/cryptsetup/cryptsetup/-/commit/52f5cb8cedf22fb3e14c744814ec8af7614146c7 | Check segment gaps regardless of heap space.
Segments are validated in hdr_validate_segments. Gaps in segment keys
are detected when collecting offsets. But if an invalid segment is very
large, larger than count, it could happen that cryptsetup is unable to
allocate enough memory, not giving a clue about what actually... | 1 | static int hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj)
{
json_object *jobj_segments, *jobj_digests, *jobj_offset, *jobj_size, *jobj_type, *jobj_flags, *jobj;
struct interval *intervals;
uint64_t offset, size;
int i, r, count, first_backup = -1;
if (!json_object_object_get_ex(hdr_jobj, "s... | 278,566,945,254,549,500,000,000,000,000,000,000,000 | luks2_json_metadata.c | 155,485,699,203,411,840,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-14382 | A vulnerability was found in upstream release cryptsetup-2.2.0 where, there's a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file 'lib/luks2/luks2_json_metadata.c' in function hdr_validate_segments(... | https://nvd.nist.gov/vuln/detail/CVE-2020-14382 |
413,283 | cryptsetup | 52f5cb8cedf22fb3e14c744814ec8af7614146c7 | https://gitlab.com/cryptsetup/cryptsetup | https://gitlab.com/cryptsetup/cryptsetup/-/commit/52f5cb8cedf22fb3e14c744814ec8af7614146c7 | Check segment gaps regardless of heap space.
Segments are validated in hdr_validate_segments. Gaps in segment keys
are detected when collecting offsets. But if an invalid segment is very
large, larger than count, it could happen that cryptsetup is unable to
allocate enough memory, not giving a clue about what actually... | 0 | static int hdr_validate_segments(struct crypt_device *cd, json_object *hdr_jobj)
{
json_object *jobj_segments, *jobj_digests, *jobj_offset, *jobj_size, *jobj_type, *jobj_flags, *jobj;
struct interval *intervals;
uint64_t offset, size;
int i, r, count, first_backup = -1;
if (!json_object_object_get_ex(hdr_jobj, "s... | 163,321,366,693,259,730,000,000,000,000,000,000,000 | luks2_json_metadata.c | 206,321,250,628,292,440,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2020-14382 | A vulnerability was found in upstream release cryptsetup-2.2.0 where, there's a bug in LUKS2 format validation code, that is effectively invoked on every device/image presenting itself as LUKS2 container. The bug is in segments validation code in file 'lib/luks2/luks2_json_metadata.c' in function hdr_validate_segments(... | https://nvd.nist.gov/vuln/detail/CVE-2020-14382 |
208,662 | libgcrypt | 8dd45ad957b54b939c288a68720137386c7f6501 | https://github.com/gpg/libgcrypt | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff;h=8dd45ad957b54b939c288a68720137386c7f6501 | random: Hash continuous areas in the csprng pool.
* random/random-csprng.c (mix_pool): Store the first hash at the end
of the pool.
--
This fixes a long standing bug (since 1998) in Libgcrypt and GnuPG.
An attacker who obtains 580 bytes of the random number from the
standard RNG can trivially predict the next 20 byte... | 1 | mix_pool(unsigned char *pool)
{
static unsigned char failsafe_digest[DIGESTLEN];
static int failsafe_digest_valid;
unsigned char *hashbuf = pool + POOLSIZE;
unsigned char *p, *pend;
int i, n;
SHA1_CONTEXT md;
unsigned int nburn;
#if DIGESTLEN != 20
#error must have a digest length of 20 for SHA-1
#endif... | 52,264,787,896,654,930,000,000,000,000,000,000,000 | random-csprng.c | 238,112,357,427,124,500,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-6313 | The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits. | https://nvd.nist.gov/vuln/detail/CVE-2016-6313 |
413,366 | libgcrypt | 8dd45ad957b54b939c288a68720137386c7f6501 | https://github.com/gpg/libgcrypt | http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff;h=8dd45ad957b54b939c288a68720137386c7f6501 | random: Hash continuous areas in the csprng pool.
* random/random-csprng.c (mix_pool): Store the first hash at the end
of the pool.
--
This fixes a long standing bug (since 1998) in Libgcrypt and GnuPG.
An attacker who obtains 580 bytes of the random number from the
standard RNG can trivially predict the next 20 byte... | 0 | mix_pool(unsigned char *pool)
{
static unsigned char failsafe_digest[DIGESTLEN];
static int failsafe_digest_valid;
unsigned char *hashbuf = pool + POOLSIZE;
unsigned char *p, *pend;
int i, n;
SHA1_CONTEXT md;
unsigned int nburn;
#if DIGESTLEN != 20
#error must have a digest length of 20 for SHA-1
#endif... | 215,811,418,281,822,970,000,000,000,000,000,000,000 | random-csprng.c | 313,429,298,554,686,500,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2016-6313 | The mixing functions in the random number generator in Libgcrypt before 1.5.6, 1.6.x before 1.6.6, and 1.7.x before 1.7.3 and GnuPG before 1.4.21 make it easier for attackers to obtain the values of 160 bits by leveraging knowledge of the previous 4640 bits. | https://nvd.nist.gov/vuln/detail/CVE-2016-6313 |
208,665 | ntp | 50ef2f62dc326bc9edac166b2b4ba5b5d8b4f7d4 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/50ef2f62dc326bc9edac166b2b4ba5b5d8b4f7d4 | [Sec 2935] use L_SUB instead of L_ISGT. Juergen Perlinger | 1 | receive(
struct recvbuf *rbufp
)
{
register struct peer *peer; /* peer structure pointer */
register struct pkt *pkt; /* receive packet pointer */
u_char hisversion; /* packet version */
u_char hisleap; /* packet leap indicator */
u_char hismode; /* packet mode */
u_char hisstratum; /* packet stratum */
u_... | 229,836,912,272,051,400,000,000,000,000,000,000,000 | ntp_proto.c | 118,907,727,771,464,170,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2015-7973 | NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network. | https://nvd.nist.gov/vuln/detail/CVE-2015-7973 |
413,389 | ntp | 50ef2f62dc326bc9edac166b2b4ba5b5d8b4f7d4 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/50ef2f62dc326bc9edac166b2b4ba5b5d8b4f7d4 | [Sec 2935] use L_SUB instead of L_ISGT. Juergen Perlinger | 0 | receive(
struct recvbuf *rbufp
)
{
register struct peer *peer; /* peer structure pointer */
register struct pkt *pkt; /* receive packet pointer */
u_char hisversion; /* packet version */
u_char hisleap; /* packet leap indicator */
u_char hismode; /* packet mode */
u_char hisstratum; /* packet stratum */
u_... | 153,109,180,639,276,770,000,000,000,000,000,000,000 | ntp_proto.c | 113,580,662,629,690,900,000,000,000,000,000,000,000 | [
"CWE-254"
] | CVE-2015-7973 | NTP before 4.2.8p6 and 4.3.x before 4.3.90, when configured in broadcast mode, allows man-in-the-middle attackers to conduct replay attacks by sniffing the network. | https://nvd.nist.gov/vuln/detail/CVE-2015-7973 |
208,666 | runc | 0a8e4117e7f715d5fbeef398405813ce8e88558b | https://github.com/opencontainers/runc | https://github.com/opencontainers/runc/commit/0a8e4117e7f715d5fbeef398405813ce8e88558b | nsenter: clone /proc/self/exe to avoid exposing host binary to container
There are quite a few circumstances where /proc/self/exe pointing to a
pretty important container binary is a _bad_ thing, so to avoid this we
have to make a copy (preferably doing self-clean-up and not being
writeable).
We require memfd_create(... | 1 | void nsexec(void)
{
int pipenum;
jmp_buf env;
int sync_child_pipe[2], sync_grandchild_pipe[2];
struct nlconfig_t config = { 0 };
/*
* If we don't have an init pipe, just return to the go routine.
* We'll only get an init pipe for start or exec.
*/
pipenum = initpipe();
if (pipenum == -1)
return;
/* Pa... | 268,755,419,852,537,260,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-5736 | runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, ... | https://nvd.nist.gov/vuln/detail/CVE-2019-5736 |
413,392 | runc | 0a8e4117e7f715d5fbeef398405813ce8e88558b | https://github.com/opencontainers/runc | https://github.com/opencontainers/runc/commit/0a8e4117e7f715d5fbeef398405813ce8e88558b | nsenter: clone /proc/self/exe to avoid exposing host binary to container
There are quite a few circumstances where /proc/self/exe pointing to a
pretty important container binary is a _bad_ thing, so to avoid this we
have to make a copy (preferably doing self-clean-up and not being
writeable).
We require memfd_create(... | 0 | void nsexec(void)
{
int pipenum;
jmp_buf env;
int sync_child_pipe[2], sync_grandchild_pipe[2];
struct nlconfig_t config = { 0 };
/*
* If we don't have an init pipe, just return to the go routine.
* We'll only get an init pipe for start or exec.
*/
pipenum = initpipe();
if (pipenum == -1)
return;
/*
... | 24,590,871,353,746,630,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-5736 | runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows attackers to overwrite the host runc binary (and consequently obtain host root access) by leveraging the ability to execute a command as root within one of these types of containers: (1) a new container with an attacker-controlled image, ... | https://nvd.nist.gov/vuln/detail/CVE-2019-5736 |
208,670 | libsoup | 0e7b2c1466434a992b6a387497432e1c97b6125c | https://git.gnome.org/browse/libsoup | https://gitlab.gnome.org/GNOME/libsoup/commit/0e7b2c1466434a992b6a387497432e1c97b6125c | NTLMv2 responses support | 1 | soup_ntlm_parse_challenge (const char *challenge,
char **nonce,
char **default_domain,
gboolean *ntlmv2_session)
{
gsize clen;
NTLMString domain;
guchar *chall;
guint32 flags;
chall = g_base64_decode (challenge, &clen);
if (clen < NTLM_CHALLENGE_DOMAIN_STRING_OFFSET ||
clen < N... | 171,827,843,952,611,940,000,000,000,000,000,000,000 | soup-auth-ntlm.c | 251,391,502,589,080,050,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-17266 | libsoup from versions 2.65.1 until 2.68.1 have a heap-based buffer over-read because soup_ntlm_parse_challenge() in soup-auth-ntlm.c does not properly check an NTLM message's length before proceeding with a memcpy. | https://nvd.nist.gov/vuln/detail/CVE-2019-17266 |
413,406 | libsoup | 0e7b2c1466434a992b6a387497432e1c97b6125c | https://git.gnome.org/browse/libsoup | https://gitlab.gnome.org/GNOME/libsoup/commit/0e7b2c1466434a992b6a387497432e1c97b6125c | NTLMv2 responses support | 0 | soup_ntlm_parse_challenge (const char *challenge,
char **nonce,
char **default_domain,
gboolean *ntlmv2_session,
gboolean *negotiate_target,
char **target_info,
size_t *target_info_sz)
{
gsize clen;
NTLMString domain;
NTLMString target;
guchar *chall;
guint32 flag... | 164,751,973,801,355,480,000,000,000,000,000,000,000 | soup-auth-ntlm.c | 252,448,962,394,453,980,000,000,000,000,000,000,000 | [
"CWE-125"
] | CVE-2019-17266 | libsoup from versions 2.65.1 until 2.68.1 have a heap-based buffer over-read because soup_ntlm_parse_challenge() in soup-auth-ntlm.c does not properly check an NTLM message's length before proceeding with a memcpy. | https://nvd.nist.gov/vuln/detail/CVE-2019-17266 |
208,671 | php-src | f938112c495b0d26572435c0be73ac0bfe642ecd | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=f938112c495b0d26572435c0be73ac0bfe642ecd | Fix bug #68819 (Fileinfo on specific file causes spurious OOM and/or segfault) | 1 |
private int
mcopy(struct magic_set *ms, union VALUETYPE *p, int type, int indir,
const unsigned char *s, uint32_t offset, size_t nbytes, struct magic *m)
{
/*
* Note: FILE_SEARCH and FILE_REGEX do not actually copy
* anything, but setup pointers into the source
*/
if (indir == 0) {
switch (type) {
case... | 123,582,188,936,573,280,000,000,000,000,000,000,000 | softmagic.c | 259,075,460,094,977,160,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-4604 | The mget function in softmagic.c in file 5.x, as used in the Fileinfo component in PHP before 5.4.40, 5.5.x before 5.5.24, and 5.6.x before 5.6.8, does not properly maintain a certain pointer relationship, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code ... | https://nvd.nist.gov/vuln/detail/CVE-2015-4604 |
413,410 | php-src | f938112c495b0d26572435c0be73ac0bfe642ecd | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=f938112c495b0d26572435c0be73ac0bfe642ecd | Fix bug #68819 (Fileinfo on specific file causes spurious OOM and/or segfault) | 0 |
private int
mcopy(struct magic_set *ms, union VALUETYPE *p, int type, int indir,
const unsigned char *s, uint32_t offset, size_t nbytes, struct magic *m)
{
/*
* Note: FILE_SEARCH and FILE_REGEX do not actually copy
* anything, but setup pointers into the source
*/
if (indir == 0) {
switch (type) {
case... | 254,907,488,341,178,640,000,000,000,000,000,000,000 | softmagic.c | 256,781,909,546,259,930,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2015-4604 | The mget function in softmagic.c in file 5.x, as used in the Fileinfo component in PHP before 5.4.40, 5.5.x before 5.5.24, and 5.6.x before 5.6.8, does not properly maintain a certain pointer relationship, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code ... | https://nvd.nist.gov/vuln/detail/CVE-2015-4604 |
208,674 | git | 3c9d0414ed2db0167e6c828b547be8fc9f88fccc | https://github.com/git/git | http://git.kernel.org/?p=git/git.git;a=commitdiff;h=3c9d0414ed2db0167e6c828b547be8fc9f88fccc;hp=c173dad58787a7f11a526dbcdaa5a2fe9ff1c87f | Check size of path buffer before writing into it
This prevents a buffer overrun that could otherwise be triggered by
creating a file called '.git' with contents
gitdir: (something really long)
Signed-off-by: Greg Brockman <gdb@mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com> | 1 | static int is_git_directory(const char *suspect)
{
char path[PATH_MAX];
size_t len = strlen(suspect);
strcpy(path, suspect);
if (getenv(DB_ENVIRONMENT)) {
if (access(getenv(DB_ENVIRONMENT), X_OK))
return 0;
}
else {
strcpy(path + len, "/objects");
if (access(path, X_OK))
return 0;
}
strcpy(path + ... | 238,750,106,386,178,100,000,000,000,000,000,000,000 | setup.c | 58,597,693,037,580,110,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2010-2542 | Stack-based buffer overflow in the is_git_directory function in setup.c in Git before 1.7.2.1 allows local users to gain privileges via a long gitdir: field in a .git file in a working copy. | https://nvd.nist.gov/vuln/detail/CVE-2010-2542 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.