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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
401,969 | libsoup | f8a54ac85eec2008c85393f331cdd251af8266ad | https://git.gnome.org/browse/libsoup | https://gitlab.gnome.org/GNOME/libsoup/commit/f8a54ac85eec2008c85393f331cdd251af8266ad | NTLM: Avoid a potential heap buffer overflow in v2 authentication
Check the length of the decoded v2 challenge before attempting to
parse it, to avoid reading past it.
Fixes #173 | 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... | 183,295,776,104,659,700,000,000,000,000,000,000,000 | soup-auth-ntlm.c | 278,935,158,739,384,200,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 |
207,882 | gimp | e3afc99b2fa7aeddf0dba4778663160a5bc682d3 | https://github.com/GNOME/gimp | http://git.gnome.org/cgit/gimp/commit/?id=e3afc99b2fa7aeddf0dba4778663160a5bc682d3 | Harden the BMP plugin against integer overflows.
Issues discovered by Stefan Cornelius, Secunia Research, advisory SA37232
and CVE identifier CVE-2009-1570. Fixes bug #600484. | 1 | ReadBMP (const gchar *name,
GError **error)
{
FILE *fd;
guchar buffer[64];
gint ColormapSize, rowbytes, Maps;
gboolean Grey = FALSE;
guchar ColorMap[256][3];
gint32 image_ID;
gchar magick[2];
Bitmap_Channel masks[4];
filename = name;
fd = g_fopen (filename, "rb... | 19,557,646,644,842,572,000,000,000,000,000,000,000 | bmp-read.c | 185,884,123,993,535,060,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2009-1570 | Integer overflow in the ReadImage function in plug-ins/file-bmp/bmp-read.c in GIMP 2.6.7 might allow remote attackers to execute arbitrary code via a BMP file with crafted width and height values that trigger a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2009-1570 |
402,675 | gimp | e3afc99b2fa7aeddf0dba4778663160a5bc682d3 | https://github.com/GNOME/gimp | http://git.gnome.org/cgit/gimp/commit/?id=e3afc99b2fa7aeddf0dba4778663160a5bc682d3 | Harden the BMP plugin against integer overflows.
Issues discovered by Stefan Cornelius, Secunia Research, advisory SA37232
and CVE identifier CVE-2009-1570. Fixes bug #600484. | 0 | ReadBMP (const gchar *name,
GError **error)
{
FILE *fd;
guchar buffer[64];
gint ColormapSize, rowbytes, Maps;
gboolean Grey = FALSE;
guchar ColorMap[256][3];
gint32 image_ID;
gchar magick[2];
Bitmap_Channel masks[4];
filename = name;
fd = g_fopen (filename, "rb... | 92,194,612,095,410,020,000,000,000,000,000,000,000 | bmp-read.c | 174,702,337,013,527,880,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2009-1570 | Integer overflow in the ReadImage function in plug-ins/file-bmp/bmp-read.c in GIMP 2.6.7 might allow remote attackers to execute arbitrary code via a BMP file with crafted width and height values that trigger a heap-based buffer overflow. | https://nvd.nist.gov/vuln/detail/CVE-2009-1570 |
207,952 | libheif | 2710c930918609caaf0a664e9c7bc3dce05d5b58 | https://github.com/strukturag/libheif | https://github.com/strukturag/libheif/commit/2710c930918609caaf0a664e9c7bc3dce05d5b58 | force fraction to a limited resolution to finally solve those pesky numerical edge cases | 1 | Fraction::Fraction(int32_t num,int32_t den)
{
int32_t g = gcd(num, den);
// these strange tests are for catching the case that we divide -2147483648 by -1,
// which would exceed the maximum positive value by one.
if (num == std::numeric_limits<int32_t>::min() && g == -1) {
num++;
}
if (den == std::nu... | 225,860,183,732,808,150,000,000,000,000,000,000,000 | box.cc | 160,179,281,520,176,020,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2020-19498 | Floating point exception in function Fraction in libheif 1.4.0, allows attackers to cause a Denial of Service or possibly other unspecified impacts. | https://nvd.nist.gov/vuln/detail/CVE-2020-19498 |
403,348 | libheif | 2710c930918609caaf0a664e9c7bc3dce05d5b58 | https://github.com/strukturag/libheif | https://github.com/strukturag/libheif/commit/2710c930918609caaf0a664e9c7bc3dce05d5b58 | force fraction to a limited resolution to finally solve those pesky numerical edge cases | 0 | Fraction::Fraction(int32_t num,int32_t den)
{
// Reduce resolution of fraction until we are in a safe range.
// We need this as adding fractions may lead to very large denominators
// (e.g. 0x10000 * 0x10000 > 0x100000000 -> overflow, leading to integer 0)
while (denominator > MAX_FRACTION_VALUE || denominator... | 289,553,661,720,379,550,000,000,000,000,000,000,000 | box.cc | 302,016,701,365,635,560,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2020-19498 | Floating point exception in function Fraction in libheif 1.4.0, allows attackers to cause a Denial of Service or possibly other unspecified impacts. | https://nvd.nist.gov/vuln/detail/CVE-2020-19498 |
207,954 | linux | 5f9562ebe710c307adc5f666bf1a2162ee7977c0 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f9562ebe710c307adc5f666bf1a2162ee7977c0 | rds: memory leak in __rds_conn_create()
__rds_conn_create() did not release conn->c_path when loop_trans != 0 and
trans->t_prefer_loopback != 0 and is_outgoing == 0.
Fixes: aced3ce57cd3 ("RDS tcp loopback connection can hang")
Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
Reviewed-by: Sharath Srinivasan <sharath.srini... | 1 | static struct rds_connection *__rds_conn_create(struct net *net,
const struct in6_addr *laddr,
const struct in6_addr *faddr,
struct rds_transport *trans,
gfp_t gfp, u8 tos,
int is_outgoing,
int dev_if)
{
struct rds_connection *conn, *parent = NULL;
struct hlist_head *head = rds_con... | 72,783,608,418,495,305,000,000,000,000,000,000,000 | connection.c | 186,523,390,708,456,260,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2021-45480 | An issue was discovered in the Linux kernel before 5.15.11. There is a memory leak in the __rds_conn_create() function in net/rds/connection.c in a certain combination of circumstances. | https://nvd.nist.gov/vuln/detail/CVE-2021-45480 |
403,379 | linux | 5f9562ebe710c307adc5f666bf1a2162ee7977c0 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5f9562ebe710c307adc5f666bf1a2162ee7977c0 | rds: memory leak in __rds_conn_create()
__rds_conn_create() did not release conn->c_path when loop_trans != 0 and
trans->t_prefer_loopback != 0 and is_outgoing == 0.
Fixes: aced3ce57cd3 ("RDS tcp loopback connection can hang")
Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
Reviewed-by: Sharath Srinivasan <sharath.srini... | 0 | static struct rds_connection *__rds_conn_create(struct net *net,
const struct in6_addr *laddr,
const struct in6_addr *faddr,
struct rds_transport *trans,
gfp_t gfp, u8 tos,
int is_outgoing,
int dev_if)
{
struct rds_connection *conn, *parent = NULL;
struct hlist_head *head = rds_con... | 10,344,279,419,048,071,000,000,000,000,000,000,000 | connection.c | 82,423,115,497,346,930,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2021-45480 | An issue was discovered in the Linux kernel before 5.15.11. There is a memory leak in the __rds_conn_create() function in net/rds/connection.c in a certain combination of circumstances. | https://nvd.nist.gov/vuln/detail/CVE-2021-45480 |
207,955 | sqlite | 522ebfa7cee96fb325a22ea3a2464a63485886a8 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/522ebfa7cee96fb325a22ea3a2464a63485886a8 | Whenever a generated column is used, assume that all columns are used.
FossilOrigin-Name: 6601da58032d18ae00b466c0f2077fb2b1ecd84225b56e1787724bea478eedc9 | 1 | static int lookupName(
Parse *pParse, /* The parsing context */
const char *zDb, /* Name of the database containing table, or NULL */
const char *zTab, /* Name of table containing column, or NULL */
const char *zCol, /* Name of the column. */
NameContext *pNC, /* The name context used to re... | 91,138,467,761,918,500,000,000,000,000,000,000,000 | resolve.c | 133,094,198,623,093,370,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19317 | lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2019-19317 |
403,395 | sqlite | 522ebfa7cee96fb325a22ea3a2464a63485886a8 | https://github.com/sqlite/sqlite | https://github.com/sqlite/sqlite/commit/522ebfa7cee96fb325a22ea3a2464a63485886a8 | Whenever a generated column is used, assume that all columns are used.
FossilOrigin-Name: 6601da58032d18ae00b466c0f2077fb2b1ecd84225b56e1787724bea478eedc9 | 0 | static int lookupName(
Parse *pParse, /* The parsing context */
const char *zDb, /* Name of the database containing table, or NULL */
const char *zTab, /* Name of table containing column, or NULL */
const char *zCol, /* Name of the column. */
NameContext *pNC, /* The name context used to re... | 12,280,224,459,486,822,000,000,000,000,000,000,000 | resolve.c | 91,079,906,539,145,000,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2019-19317 | lookupName in resolve.c in SQLite 3.30.1 omits bits from the colUsed bitmask in the case of a generated column, which allows attackers to cause a denial of service or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2019-19317 |
207,963 | curl | b5f947b8ac0e282c61c75b69cd5b9d37dafc6959 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/b5f947b8ac0e282c61c75b69cd5b9d37dafc6959 | cookie: cookie parser out of boundary memory access
The internal libcurl function called sanitize_cookie_path() that cleans
up the path element as given to it from a remote site or when read from
a file, did not properly validate the input. If given a path that
consisted of a single double-quote, libcurl would index a... | 1 | static char *sanitize_cookie_path(const char *cookie_path)
{
size_t len;
char *new_path = strdup(cookie_path);
if(!new_path)
return NULL;
/* some stupid site sends path attribute with '"'. */
if(new_path[0] == '\"') {
memmove((void *)new_path, (const void *)(new_path + 1), strlen(new_path));
}
if... | 334,708,896,492,439,450,000,000,000,000,000,000,000 | cookie.c | 168,932,175,234,390,730,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3145 | The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds write and crash) or possibly have other unspecified impact via a cookie path containing only a double-quote character. | https://nvd.nist.gov/vuln/detail/CVE-2015-3145 |
403,482 | curl | b5f947b8ac0e282c61c75b69cd5b9d37dafc6959 | https://github.com/curl/curl | https://github.com/bagder/curl/commit/b5f947b8ac0e282c61c75b69cd5b9d37dafc6959 | cookie: cookie parser out of boundary memory access
The internal libcurl function called sanitize_cookie_path() that cleans
up the path element as given to it from a remote site or when read from
a file, did not properly validate the input. If given a path that
consisted of a single double-quote, libcurl would index a... | 0 | static char *sanitize_cookie_path(const char *cookie_path)
{
size_t len;
char *new_path = strdup(cookie_path);
if(!new_path)
return NULL;
/* some stupid site sends path attribute with '"'. */
len = strlen(new_path);
if(new_path[0] == '\"') {
memmove((void *)new_path, (const void *)(new_path + 1), l... | 245,805,195,672,538,600,000,000,000,000,000,000,000 | cookie.c | 44,707,159,199,394,280,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2015-3145 | The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds write and crash) or possibly have other unspecified impact via a cookie path containing only a double-quote character. | https://nvd.nist.gov/vuln/detail/CVE-2015-3145 |
207,977 | net | 36d5fe6a000790f56039afe26834265db0a3ad4c | https://git.kernel.org/cgit/linux/kernel/git/davem/net | https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=36d5fe6a000790f56039afe26834265db0a3ad4c | core, nfqueue, openvswitch: Orphan frags in skb_zerocopy and handle errors
skb_zerocopy can copy elements of the frags array between skbs, but it doesn't
orphan them. Also, it doesn't handle errors, so this patch takes care of that
as well, and modify the callers accordingly. skb_tx_error() is also added to
the caller... | 1 | nfqnl_build_packet_message(struct net *net, struct nfqnl_instance *queue,
struct nf_queue_entry *entry,
__be32 **packet_id_ptr)
{
size_t size;
size_t data_len = 0, cap_len = 0;
unsigned int hlen = 0;
struct sk_buff *skb;
struct nlattr *nla;
struct nfqnl_msg_packet_hdr *pmsg;
struct nlmsghdr *nlh;
st... | 65,155,167,937,380,820,000,000,000,000,000,000,000 | nfnetlink_queue_core.c | 158,609,396,198,116,120,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2014-2568 | Use-after-free vulnerability in the nfqnl_zcopy function in net/netfilter/nfnetlink_queue_core.c in the Linux kernel through 3.13.6 allows attackers to obtain sensitive information from kernel memory by leveraging the absence of a certain orphaning operation. NOTE: the affected code was moved to the skb_zerocopy functi... | https://nvd.nist.gov/vuln/detail/CVE-2014-2568 |
403,923 | net | 36d5fe6a000790f56039afe26834265db0a3ad4c | https://git.kernel.org/cgit/linux/kernel/git/davem/net | https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=36d5fe6a000790f56039afe26834265db0a3ad4c | core, nfqueue, openvswitch: Orphan frags in skb_zerocopy and handle errors
skb_zerocopy can copy elements of the frags array between skbs, but it doesn't
orphan them. Also, it doesn't handle errors, so this patch takes care of that
as well, and modify the callers accordingly. skb_tx_error() is also added to
the caller... | 0 | nfqnl_build_packet_message(struct net *net, struct nfqnl_instance *queue,
struct nf_queue_entry *entry,
__be32 **packet_id_ptr)
{
size_t size;
size_t data_len = 0, cap_len = 0;
unsigned int hlen = 0;
struct sk_buff *skb;
struct nlattr *nla;
struct nfqnl_msg_packet_hdr *pmsg;
struct nlmsghdr *nlh;
st... | 256,727,174,022,692,900,000,000,000,000,000,000,000 | nfnetlink_queue_core.c | 302,829,932,919,269,580,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2014-2568 | Use-after-free vulnerability in the nfqnl_zcopy function in net/netfilter/nfnetlink_queue_core.c in the Linux kernel through 3.13.6 allows attackers to obtain sensitive information from kernel memory by leveraging the absence of a certain orphaning operation. NOTE: the affected code was moved to the skb_zerocopy functi... | https://nvd.nist.gov/vuln/detail/CVE-2014-2568 |
207,981 | edk2 | 26442d11e620a9e81c019a24a4ff38441c64ba10 | https://github.com/tianocore/edk2 | https://github.com/tianocore/edk2/commit/26442d11e620a9e81c019a24a4ff38441c64ba10 | CryptoPkg/BaseCryptLib: fix NULL dereference (CVE-2019-14584)
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1914
AuthenticodeVerify() calls OpenSSLs d2i_PKCS7() API to parse asn encoded
signed authenticode pkcs#7 data. when this successfully returns, a type
check is done by calling PKCS7_type_is_signed() and th... | 1 | AuthenticodeVerify (
IN CONST UINT8 *AuthData,
IN UINTN DataSize,
IN CONST UINT8 *TrustedCert,
IN UINTN CertSize,
IN CONST UINT8 *ImageHash,
IN UINTN HashSize
)
{
BOOLEAN Status;
PKCS7 *Pkcs7;
CONST UINT8 *Temp;
CONST UINT8 *OrigAuthData;
... | 283,238,032,623,066,600,000,000,000,000,000,000,000 | CryptAuthenticode.c | 123,998,382,412,390,180,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14584 | Null pointer dereference in Tianocore EDK2 may allow an authenticated user to potentially enable escalation of privilege via local access. | https://nvd.nist.gov/vuln/detail/CVE-2019-14584 |
404,042 | edk2 | 26442d11e620a9e81c019a24a4ff38441c64ba10 | https://github.com/tianocore/edk2 | https://github.com/tianocore/edk2/commit/26442d11e620a9e81c019a24a4ff38441c64ba10 | CryptoPkg/BaseCryptLib: fix NULL dereference (CVE-2019-14584)
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1914
AuthenticodeVerify() calls OpenSSLs d2i_PKCS7() API to parse asn encoded
signed authenticode pkcs#7 data. when this successfully returns, a type
check is done by calling PKCS7_type_is_signed() and th... | 0 | AuthenticodeVerify (
IN CONST UINT8 *AuthData,
IN UINTN DataSize,
IN CONST UINT8 *TrustedCert,
IN UINTN CertSize,
IN CONST UINT8 *ImageHash,
IN UINTN HashSize
)
{
BOOLEAN Status;
PKCS7 *Pkcs7;
CONST UINT8 *Temp;
CONST UINT8 *OrigAuthData;
... | 93,921,843,837,404,800,000,000,000,000,000,000,000 | CryptAuthenticode.c | 310,287,381,444,382,060,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2019-14584 | Null pointer dereference in Tianocore EDK2 may allow an authenticated user to potentially enable escalation of privilege via local access. | https://nvd.nist.gov/vuln/detail/CVE-2019-14584 |
207,986 | Pillow | a130c45990578a1bb0a6a000ed1b110e27324910 | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/a130c45990578a1bb0a6a000ed1b110e27324910 | add several TIFF decoders and encoders | 1 | PyImaging_LibTiffDecoderNew(PyObject* self, PyObject* args)
{
ImagingDecoderObject* decoder;
char* mode;
char* rawmode;
char* compname;
int compression;
int fp;
if (! PyArg_ParseTuple(args, "sssi", &mode, &rawmode, &compname, &fp))
return NULL;
TRACE(("new tiff decoder %s\n", c... | 313,204,545,325,708,100,000,000,000,000,000,000,000 | decode.c | 338,565,394,641,491,240,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-0740 | Buffer overflow in the ImagingLibTiffDecode function in libImaging/TiffDecode.c in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2016-0740 |
404,125 | Pillow | a130c45990578a1bb0a6a000ed1b110e27324910 | https://github.com/python-pillow/Pillow | https://github.com/python-pillow/Pillow/commit/a130c45990578a1bb0a6a000ed1b110e27324910 | add several TIFF decoders and encoders | 0 | PyImaging_LibTiffDecoderNew(PyObject* self, PyObject* args)
{
ImagingDecoderObject* decoder;
char* mode;
char* rawmode;
char* compname;
int compression;
int fp;
if (! PyArg_ParseTuple(args, "sssi", &mode, &rawmode, &compname, &fp))
return NULL;
TRACE(("new tiff decoder %s\n", c... | 103,338,941,034,641,960,000,000,000,000,000,000,000 | decode.c | 165,896,498,721,646,730,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-0740 | Buffer overflow in the ImagingLibTiffDecode function in libImaging/TiffDecode.c in Pillow before 3.1.1 allows remote attackers to overwrite memory via a crafted TIFF file. | https://nvd.nist.gov/vuln/detail/CVE-2016-0740 |
207,987 | libxml2 | a436374994c47b12d5de1b8b1d191a098fa23594 | https://github.com/GNOME/libxml2 | https://gitlab.gnome.org/GNOME/libxml2/commit/a436374994c47b12d5de1b8b1d191a098fa23594 | Fix nullptr deref with XPath logic ops
If the XPath stack is corrupted, for example by a misbehaving extension
function, the "and" and "or" XPath operators could dereference NULL
pointers. Check that the XPath stack isn't empty and optimize the
logic operators slightly.
Closes: https://gitlab.gnome.org/GNOME/libxml2/... | 1 | */
static int
xmlXPathCompOpEval(xmlXPathParserContextPtr ctxt, xmlXPathStepOpPtr op)
{
int total = 0;
int equal, ret;
xmlXPathCompExprPtr comp;
xmlXPathObjectPtr arg1, arg2;
CHECK_ERROR0;
comp = ctxt->comp;
switch (op->op) {
case XPATH_OP_END:
return (0);
case ... | 322,698,077,407,714,130,000,000,000,000,000,000,000 | xpath.c | 37,345,707,473,691,810,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-14404 | A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of... | https://nvd.nist.gov/vuln/detail/CVE-2018-14404 |
404,174 | libxml2 | a436374994c47b12d5de1b8b1d191a098fa23594 | https://github.com/GNOME/libxml2 | https://gitlab.gnome.org/GNOME/libxml2/commit/a436374994c47b12d5de1b8b1d191a098fa23594 | Fix nullptr deref with XPath logic ops
If the XPath stack is corrupted, for example by a misbehaving extension
function, the "and" and "or" XPath operators could dereference NULL
pointers. Check that the XPath stack isn't empty and optimize the
logic operators slightly.
Closes: https://gitlab.gnome.org/GNOME/libxml2/... | 0 | */
static int
xmlXPathCompOpEval(xmlXPathParserContextPtr ctxt, xmlXPathStepOpPtr op)
{
int total = 0;
int equal, ret;
xmlXPathCompExprPtr comp;
xmlXPathObjectPtr arg1, arg2;
CHECK_ERROR0;
comp = ctxt->comp;
switch (op->op) {
case XPATH_OP_END:
return (0);
case ... | 61,710,995,246,283,580,000,000,000,000,000,000,000 | xpath.c | 142,424,064,680,958,910,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-14404 | A NULL pointer dereference vulnerability exists in the xpath.c:xmlXPathCompOpEval() function of libxml2 through 2.9.8 when parsing an invalid XPath expression in the XPATH_OP_AND or XPATH_OP_OR case. Applications processing untrusted XSL format inputs with the use of the libxml2 library may be vulnerable to a denial of... | https://nvd.nist.gov/vuln/detail/CVE-2018-14404 |
208,026 | bpf | c4eb1f403243fc7bbb7de644db8587c03de36da6 | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=c4eb1f403243fc7bbb7de644db8587c03de36da6 | bpf: Fix integer overflow involving bucket_size
In __htab_map_lookup_and_delete_batch(), hash buckets are iterated
over to count the number of elements in each bucket (bucket_size).
If bucket_size is large enough, the multiplication to calculate
kvmalloc() size could overflow, resulting in out-of-bounds write
as repor... | 1 | __htab_map_lookup_and_delete_batch(struct bpf_map *map,
const union bpf_attr *attr,
union bpf_attr __user *uattr,
bool do_delete, bool is_lru_map,
bool is_percpu)
{
struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
u32 bucket_cnt, total, key_size, value_size, roundup_key_siz... | 241,049,394,282,116,760,000,000,000,000,000,000,000 | hashtab.c | 43,090,817,508,001,120,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-38166 | In kernel/bpf/hashtab.c in the Linux kernel through 5.13.8, there is an integer overflow and out-of-bounds write when many elements are placed in a single bucket. NOTE: exploitation might be impractical without the CAP_SYS_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2021-38166 |
404,336 | bpf | c4eb1f403243fc7bbb7de644db8587c03de36da6 | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf | https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=c4eb1f403243fc7bbb7de644db8587c03de36da6 | bpf: Fix integer overflow involving bucket_size
In __htab_map_lookup_and_delete_batch(), hash buckets are iterated
over to count the number of elements in each bucket (bucket_size).
If bucket_size is large enough, the multiplication to calculate
kvmalloc() size could overflow, resulting in out-of-bounds write
as repor... | 0 | __htab_map_lookup_and_delete_batch(struct bpf_map *map,
const union bpf_attr *attr,
union bpf_attr __user *uattr,
bool do_delete, bool is_lru_map,
bool is_percpu)
{
struct bpf_htab *htab = container_of(map, struct bpf_htab, map);
u32 bucket_cnt, total, key_size, value_size, roundup_key_siz... | 189,810,025,715,008,070,000,000,000,000,000,000,000 | hashtab.c | 151,088,235,682,827,830,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-38166 | In kernel/bpf/hashtab.c in the Linux kernel through 5.13.8, there is an integer overflow and out-of-bounds write when many elements are placed in a single bucket. NOTE: exploitation might be impractical without the CAP_SYS_ADMIN capability. | https://nvd.nist.gov/vuln/detail/CVE-2021-38166 |
208,027 | libvpx | 52add5896661d186dec284ed646a4b33b607d2c7 | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/52add5896661d186dec284ed646a4b33b607d2c7 | VP8: Fix use-after-free in postproc.
The pointer in vp8 postproc refers to show_frame_mi which is only
updated on show frame. However, when there is a no-show frame which also
changes the size (thus new frame buffers allocated), show_frame_mi is
not updated with new frame buffer memory.
Change the pointer in postproc... | 1 | void vp8_deblock(VP8_COMMON *cm, YV12_BUFFER_CONFIG *source,
YV12_BUFFER_CONFIG *post, int q, int low_var_thresh,
int flag) {
double level = 6.0e-05 * q * q * q - .0067 * q * q + .306 * q + .0065;
int ppl = (int)(level + .5);
const MODE_INFO *mode_info_context = cm->show_frame_m... | 218,312,295,796,889,030,000,000,000,000,000,000,000 | postproc.c | 221,660,975,016,671,230,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-9433 | In libvpx, there is a possible information disclosure due to improper input validation. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-80479354 | https://nvd.nist.gov/vuln/detail/CVE-2019-9433 |
404,361 | libvpx | 52add5896661d186dec284ed646a4b33b607d2c7 | https://github.com/webmproject/libvpx | https://github.com/webmproject/libvpx/commit/52add5896661d186dec284ed646a4b33b607d2c7 | VP8: Fix use-after-free in postproc.
The pointer in vp8 postproc refers to show_frame_mi which is only
updated on show frame. However, when there is a no-show frame which also
changes the size (thus new frame buffers allocated), show_frame_mi is
not updated with new frame buffer memory.
Change the pointer in postproc... | 0 | void vp8_deblock(VP8_COMMON *cm, YV12_BUFFER_CONFIG *source,
YV12_BUFFER_CONFIG *post, int q, int low_var_thresh,
int flag) {
double level = 6.0e-05 * q * q * q - .0067 * q * q + .306 * q + .0065;
int ppl = (int)(level + .5);
const MODE_INFO *mode_info_context = cm->mi;
int mb... | 7,945,075,896,909,699,000,000,000,000,000,000,000 | postproc.c | 61,178,464,384,640,030,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-9433 | In libvpx, there is a possible information disclosure due to improper input validation. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-80479354 | https://nvd.nist.gov/vuln/detail/CVE-2019-9433 |
208,030 | ImageMagick6 | 3449a06f0122d4d9e68b4739417a3eaad0b24265 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/3449a06f0122d4d9e68b4739417a3eaad0b24265 | https://github.com/ImageMagick/ImageMagick/issues/1201 | 1 | static Image *ReadOneJNGImage(MngInfo *mng_info,
const ImageInfo *image_info, ExceptionInfo *exception)
{
Image
*alpha_image,
*color_image,
*image,
*jng_image;
ImageInfo
*alpha_image_info,
*color_image_info;
MagickBooleanType
logging;
int
unique_filenames;
ssize_t
y... | 56,536,873,315,672,450,000,000,000,000,000,000,000 | png.c | 73,009,530,751,599,190,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2018-16640 | ImageMagick 7.0.8-5 has a memory leak vulnerability in the function ReadOneJNGImage in coders/png.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-16640 |
404,395 | ImageMagick6 | 3449a06f0122d4d9e68b4739417a3eaad0b24265 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/3449a06f0122d4d9e68b4739417a3eaad0b24265 | https://github.com/ImageMagick/ImageMagick/issues/1201 | 0 | static Image *ReadOneJNGImage(MngInfo *mng_info,
const ImageInfo *image_info, ExceptionInfo *exception)
{
Image
*alpha_image,
*color_image,
*image,
*jng_image;
ImageInfo
*alpha_image_info,
*color_image_info;
MagickBooleanType
logging;
int
unique_filenames;
ssize_t
y... | 127,203,639,142,040,550,000,000,000,000,000,000,000 | png.c | 278,826,159,293,656,000,000,000,000,000,000,000,000 | [
"CWE-772"
] | CVE-2018-16640 | ImageMagick 7.0.8-5 has a memory leak vulnerability in the function ReadOneJNGImage in coders/png.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-16640 |
208,031 | linux | a0ecd6fdbf5d648123a7315c695fb6850d702835 | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a0ecd6fdbf5d648123a7315c695fb6850d702835 | drm/komeda: prevent memory leak in komeda_wb_connector_add
In komeda_wb_connector_add if drm_writeback_connector_init fails the
allocated memory for kwb_conn should be released.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Reviewed-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
Sig... | 1 | static int komeda_wb_connector_add(struct komeda_kms_dev *kms,
struct komeda_crtc *kcrtc)
{
struct komeda_dev *mdev = kms->base.dev_private;
struct komeda_wb_connector *kwb_conn;
struct drm_writeback_connector *wb_conn;
u32 *formats, n_formats = 0;
int err;
if (!kcrtc->master->wb_layer)
return 0;
kwb_... | 285,438,793,934,963,930,000,000,000,000,000,000,000 | komeda_wb_connector.c | 150,188,300,861,623,690,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-18810 | A memory leak in the komeda_wb_connector_add() function in drivers/gpu/drm/arm/display/komeda/komeda_wb_connector.c in the Linux kernel before 5.3.8 allows attackers to cause a denial of service (memory consumption) by triggering drm_writeback_connector_init() failures, aka CID-a0ecd6fdbf5d. | https://nvd.nist.gov/vuln/detail/CVE-2019-18810 |
404,400 | linux | a0ecd6fdbf5d648123a7315c695fb6850d702835 | https://github.com/torvalds/linux | https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a0ecd6fdbf5d648123a7315c695fb6850d702835 | drm/komeda: prevent memory leak in komeda_wb_connector_add
In komeda_wb_connector_add if drm_writeback_connector_init fails the
allocated memory for kwb_conn should be released.
Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
Reviewed-by: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
Sig... | 0 | static int komeda_wb_connector_add(struct komeda_kms_dev *kms,
struct komeda_crtc *kcrtc)
{
struct komeda_dev *mdev = kms->base.dev_private;
struct komeda_wb_connector *kwb_conn;
struct drm_writeback_connector *wb_conn;
u32 *formats, n_formats = 0;
int err;
if (!kcrtc->master->wb_layer)
return 0;
kwb_... | 270,109,454,645,402,080,000,000,000,000,000,000,000 | komeda_wb_connector.c | 102,077,125,847,281,900,000,000,000,000,000,000,000 | [
"CWE-401"
] | CVE-2019-18810 | A memory leak in the komeda_wb_connector_add() function in drivers/gpu/drm/arm/display/komeda/komeda_wb_connector.c in the Linux kernel before 5.3.8 allows attackers to cause a denial of service (memory consumption) by triggering drm_writeback_connector_init() failures, aka CID-a0ecd6fdbf5d. | https://nvd.nist.gov/vuln/detail/CVE-2019-18810 |
208,032 | ntp | 184516e143ce4448ddb5b9876dd372008cc779f6 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/184516e143ce4448ddb5b9876dd372008cc779f6 | [TALOS-CAN-0062] prevent directory traversal for VMS, too, when using 'saveconfig' command. | 1 | save_config(
struct recvbuf *rbufp,
int restrict_mask
)
{
char reply[128];
#ifdef SAVECONFIG
char filespec[128];
char filename[128];
char fullpath[512];
const char savedconfig_eq[] = "savedconfig=";
char savedconfig[sizeof(savedconfig_eq) + sizeof(filename)];
time_t now;
int fd;
FILE *fptr;
#endif
if (RES... | 180,551,050,337,518,400,000,000,000,000,000,000,000 | ntp_control.c | 154,196,215,437,361,830,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2015-7851 | Directory traversal vulnerability in the save_config function in ntpd in ntp_control.c in NTP before 4.2.8p4, when used on systems that do not use '\' or '/' characters for directory separation such as OpenVMS, allows remote authenticated users to overwrite arbitrary files. | https://nvd.nist.gov/vuln/detail/CVE-2015-7851 |
404,409 | ntp | 184516e143ce4448ddb5b9876dd372008cc779f6 | https://github.com/ntp-project/ntp | https://github.com/ntp-project/ntp/commit/184516e143ce4448ddb5b9876dd372008cc779f6 | [TALOS-CAN-0062] prevent directory traversal for VMS, too, when using 'saveconfig' command. | 0 | save_config(
struct recvbuf *rbufp,
int restrict_mask
)
{
/* block directory traversal by searching for characters that
* indicate directory components in a file path.
*
* Conceptually we should be searching for DIRSEP in filename,
* however Windows actually recognizes both forward and
* backslashes as eq... | 306,278,211,289,822,860,000,000,000,000,000,000,000 | ntp_control.c | 69,878,050,915,336,760,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2015-7851 | Directory traversal vulnerability in the save_config function in ntpd in ntp_control.c in NTP before 4.2.8p4, when used on systems that do not use '\' or '/' characters for directory separation such as OpenVMS, allows remote authenticated users to overwrite arbitrary files. | https://nvd.nist.gov/vuln/detail/CVE-2015-7851 |
208,054 | libevent | 841ecbd96105c84ac2e7c9594aeadbcc6fb38bc4 | https://github.com/libevent/libevent | https://github.com/libevent/libevent/commit/841ecbd96105c84ac2e7c9594aeadbcc6fb38bc4 | Fix CVE-2014-6272 in Libevent 2.1
For this fix, we need to make sure that passing too-large inputs to
the evbuffer functions can't make us do bad things with the heap.
Also, lower the maximum chunk size to the lower of off_t, size_t maximum.
This is necessary since otherwise we could get into an infinite loop
if we ... | 1 | evbuffer_add(struct evbuffer *buf, const void *data_in, size_t datlen)
{
struct evbuffer_chain *chain, *tmp;
const unsigned char *data = data_in;
size_t remain, to_alloc;
int result = -1;
EVBUFFER_LOCK(buf);
if (buf->freeze_end) {
goto done;
}
chain = buf->last;
/* If there are no chains allocated for th... | 105,676,171,071,365,520,000,000,000,000,000,000,000 | buffer.c | 337,089,390,499,070,260,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-6272 | Multiple integer overflows in the evbuffer API in Libevent 1.4.x before 1.4.15, 2.0.x before 2.0.22, and 2.1.x before 2.1.5-beta allow context-dependent attackers to cause a denial of service or possibly have other unspecified impact via "insanely large inputs" to the (1) evbuffer_add, (2) evbuffer_expand, or (3) buffe... | https://nvd.nist.gov/vuln/detail/CVE-2014-6272 |
404,471 | libevent | 841ecbd96105c84ac2e7c9594aeadbcc6fb38bc4 | https://github.com/libevent/libevent | https://github.com/libevent/libevent/commit/841ecbd96105c84ac2e7c9594aeadbcc6fb38bc4 | Fix CVE-2014-6272 in Libevent 2.1
For this fix, we need to make sure that passing too-large inputs to
the evbuffer functions can't make us do bad things with the heap.
Also, lower the maximum chunk size to the lower of off_t, size_t maximum.
This is necessary since otherwise we could get into an infinite loop
if we ... | 0 | evbuffer_add(struct evbuffer *buf, const void *data_in, size_t datlen)
{
struct evbuffer_chain *chain, *tmp;
const unsigned char *data = data_in;
size_t remain, to_alloc;
int result = -1;
EVBUFFER_LOCK(buf);
if (buf->freeze_end) {
goto done;
}
/* Prevent buf->total_len overflow */
if (datlen > EV_SIZE_MAX ... | 273,198,385,200,951,070,000,000,000,000,000,000,000 | buffer.c | 322,769,811,334,822,130,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-6272 | Multiple integer overflows in the evbuffer API in Libevent 1.4.x before 1.4.15, 2.0.x before 2.0.22, and 2.1.x before 2.1.5-beta allow context-dependent attackers to cause a denial of service or possibly have other unspecified impact via "insanely large inputs" to the (1) evbuffer_add, (2) evbuffer_expand, or (3) buffe... | https://nvd.nist.gov/vuln/detail/CVE-2014-6272 |
208,070 | vim | 64066b9acd9f8cffdf4840f797748f938a13f2d6 | https://github.com/vim/vim | https://github.com/vim/vim/commit/64066b9acd9f8cffdf4840f797748f938a13f2d6 | patch 8.2.3612: using freed memory with regexp using a mark
Problem: Using freed memory with regexp using a mark.
Solution: Get the line again after getting the mark position. | 1 | nfa_regmatch(
nfa_regprog_T *prog,
nfa_state_T *start,
regsubs_T *submatch,
regsubs_T *m)
{
int result = FALSE;
size_t size = 0;
int flag = 0;
int go_to_nextline = FALSE;
nfa_thread_T *t;
nfa_list_T list[2];
int listidx;
nfa_list_T *thislist;
nfa_list_T *nextli... | 48,313,578,703,462,120,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2021-3974 | vim is vulnerable to Use After Free | https://nvd.nist.gov/vuln/detail/CVE-2021-3974 |
404,511 | vim | 64066b9acd9f8cffdf4840f797748f938a13f2d6 | https://github.com/vim/vim | https://github.com/vim/vim/commit/64066b9acd9f8cffdf4840f797748f938a13f2d6 | patch 8.2.3612: using freed memory with regexp using a mark
Problem: Using freed memory with regexp using a mark.
Solution: Get the line again after getting the mark position. | 0 | nfa_regmatch(
nfa_regprog_T *prog,
nfa_state_T *start,
regsubs_T *submatch,
regsubs_T *m)
{
int result = FALSE;
size_t size = 0;
int flag = 0;
int go_to_nextline = FALSE;
nfa_thread_T *t;
nfa_list_T list[2];
int listidx;
nfa_list_T *thislist;
nfa_list_T *nextli... | 127,303,135,429,757,570,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2021-3974 | vim is vulnerable to Use After Free | https://nvd.nist.gov/vuln/detail/CVE-2021-3974 |
208,074 | linux | 51b00d8509dc69c98740da2ad07308b630d3eb7d | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/gvt/kvmgt.c?id=51b00d8509dc69c98740da2ad07308b630d3eb7d | drm/i915/gvt: Fix mmap range check
This is to fix missed mmap range check on vGPU bar2 region
and only allow to map vGPU allocated GMADDR range, which means
user space should support sparse mmap to get proper offset for
mmap vGPU aperture. And this takes care of actual pgoff in mmap
request as original code always doe... | 1 | static int intel_vgpu_mmap(struct mdev_device *mdev, struct vm_area_struct *vma)
{
unsigned int index;
u64 virtaddr;
unsigned long req_size, pgoff = 0;
pgprot_t pg_prot;
struct intel_vgpu *vgpu = mdev_get_drvdata(mdev);
index = vma->vm_pgoff >> (VFIO_PCI_OFFSET_SHIFT - PAGE_SHIFT);
if (index >= VFIO_PCI_ROM_REG... | 255,591,591,351,171,930,000,000,000,000,000,000,000 | kvmgt.c | 335,661,794,489,880,240,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-11085 | Insufficient input validation in Kernel Mode Driver in Intel(R) i915 Graphics for Linux before version 5.0 may allow an authenticated user to potentially enable escalation of privilege via local access. | https://nvd.nist.gov/vuln/detail/CVE-2019-11085 |
404,560 | linux | 51b00d8509dc69c98740da2ad07308b630d3eb7d | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/gvt/kvmgt.c?id=51b00d8509dc69c98740da2ad07308b630d3eb7d | drm/i915/gvt: Fix mmap range check
This is to fix missed mmap range check on vGPU bar2 region
and only allow to map vGPU allocated GMADDR range, which means
user space should support sparse mmap to get proper offset for
mmap vGPU aperture. And this takes care of actual pgoff in mmap
request as original code always doe... | 0 | static int intel_vgpu_mmap(struct mdev_device *mdev, struct vm_area_struct *vma)
{
unsigned int index;
u64 virtaddr;
unsigned long req_size, pgoff, req_start;
pgprot_t pg_prot;
struct intel_vgpu *vgpu = mdev_get_drvdata(mdev);
index = vma->vm_pgoff >> (VFIO_PCI_OFFSET_SHIFT - PAGE_SHIFT);
if (index >= VFIO_PCI_... | 36,993,616,042,280,780,000,000,000,000,000,000,000 | kvmgt.c | 266,453,787,761,583,500,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2019-11085 | Insufficient input validation in Kernel Mode Driver in Intel(R) i915 Graphics for Linux before version 5.0 may allow an authenticated user to potentially enable escalation of privilege via local access. | https://nvd.nist.gov/vuln/detail/CVE-2019-11085 |
208,089 | flac | 5a365996d739bdf4711af51d9c2c71c8a5e14660 | https://github.com/xiph/flac | https://git.xiph.org/?p=flac.git;a=commit;h=5a365996d739bdf4711af51d9c2c71c8a5e14660 | src/libFLAC/stream_decoder.c : Fail safely to avoid a heap overflow.
This fix is closely related to the fix for CVE-2014-9028. When that
fix went public Miroslav Lichvar noticed a similar potential problem
spot in the same function and was able to craft a file to trigger a
heap write overflow.
Reported-by : Miroslav ... | 1 | FLAC__bool read_residual_partitioned_rice_(FLAC__StreamDecoder *decoder, unsigned predictor_order, unsigned partition_order, FLAC__EntropyCodingMethod_PartitionedRiceContents *partitioned_rice_contents, FLAC__int32 *residual, FLAC__bool is_extended)
{
FLAC__uint32 rice_parameter;
int i;
unsigned partition, sample, u... | 255,673,385,725,319,770,000,000,000,000,000,000,000 | stream_decoder.c | 106,767,477,038,638,050,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-9028 | Heap-based buffer overflow in stream_decoder.c in libFLAC before 1.3.1 allows remote attackers to execute arbitrary code via a crafted .flac file. | https://nvd.nist.gov/vuln/detail/CVE-2014-9028 |
404,869 | flac | 5a365996d739bdf4711af51d9c2c71c8a5e14660 | https://github.com/xiph/flac | https://git.xiph.org/?p=flac.git;a=commit;h=5a365996d739bdf4711af51d9c2c71c8a5e14660 | src/libFLAC/stream_decoder.c : Fail safely to avoid a heap overflow.
This fix is closely related to the fix for CVE-2014-9028. When that
fix went public Miroslav Lichvar noticed a similar potential problem
spot in the same function and was able to craft a file to trigger a
heap write overflow.
Reported-by : Miroslav ... | 0 | FLAC__bool read_residual_partitioned_rice_(FLAC__StreamDecoder *decoder, unsigned predictor_order, unsigned partition_order, FLAC__EntropyCodingMethod_PartitionedRiceContents *partitioned_rice_contents, FLAC__int32 *residual, FLAC__bool is_extended)
{
FLAC__uint32 rice_parameter;
int i;
unsigned partition, sample, u... | 108,288,480,552,102,290,000,000,000,000,000,000,000 | stream_decoder.c | 13,260,615,516,800,810,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2014-9028 | Heap-based buffer overflow in stream_decoder.c in libFLAC before 1.3.1 allows remote attackers to execute arbitrary code via a crafted .flac file. | https://nvd.nist.gov/vuln/detail/CVE-2014-9028 |
208,090 | libplist | fdebf8b319b9280cd0e9b4382f2c7cbf26ef9325 | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/fdebf8b319b9280cd0e9b4382f2c7cbf26ef9325 | bplist: Fix integer overflow check (offset table size) | 1 | PLIST_API void plist_from_bin(const char *plist_bin, uint32_t length, plist_t * plist)
{
bplist_trailer_t *trailer = NULL;
uint8_t offset_size = 0;
uint8_t ref_size = 0;
uint64_t num_objects = 0;
uint64_t root_object = 0;
const char *offset_table = NULL;
const char *start_data = NULL;
co... | 316,508,634,318,079,170,000,000,000,000,000,000,000 | bplist.c | 127,137,343,021,602,020,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-7982 | Integer overflow in the plist_from_bin function in bplist.c in libimobiledevice/libplist before 2017-04-19 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted plist file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7982 |
404,877 | libplist | fdebf8b319b9280cd0e9b4382f2c7cbf26ef9325 | https://github.com/libimobiledevice/libplist | https://github.com/libimobiledevice/libplist/commit/fdebf8b319b9280cd0e9b4382f2c7cbf26ef9325 | bplist: Fix integer overflow check (offset table size) | 0 | PLIST_API void plist_from_bin(const char *plist_bin, uint32_t length, plist_t * plist)
{
bplist_trailer_t *trailer = NULL;
uint8_t offset_size = 0;
uint8_t ref_size = 0;
uint64_t num_objects = 0;
uint64_t root_object = 0;
const char *offset_table = NULL;
uint64_t offset_table_size = 0;
c... | 126,751,213,189,194,020,000,000,000,000,000,000,000 | bplist.c | 300,880,929,394,860,640,000,000,000,000,000,000,000 | [
"CWE-190"
] | CVE-2017-7982 | Integer overflow in the plist_from_bin function in bplist.c in libimobiledevice/libplist before 2017-04-19 allows remote attackers to cause a denial of service (heap-based buffer over-read and application crash) via a crafted plist file. | https://nvd.nist.gov/vuln/detail/CVE-2017-7982 |
208,092 | ImageMagick | 787ee25e9fb0e4e0509121342371d925fe5044f8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/787ee25e9fb0e4e0509121342371d925fe5044f8 | https://github.com/ImageMagick/ImageMagick/issues/537 | 1 | static Image *ReadPESImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MagickPathExtent];
FILE
*file;
Image
*image;
ImageInfo
*read_info;
int
delta_x,
delta_y,
j,
unique_file,
x,
y;
MagickBooleanType
status;
PESBlockInfo
block... | 191,946,446,374,316,160,000,000,000,000,000,000,000 | pes.c | 232,173,139,370,490,930,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-11446 | The ReadPESImage function in coders\pes.c in ImageMagick 7.0.6-1 has an infinite loop vulnerability that can cause CPU exhaustion via a crafted PES file. | https://nvd.nist.gov/vuln/detail/CVE-2017-11446 |
404,990 | ImageMagick | 787ee25e9fb0e4e0509121342371d925fe5044f8 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/787ee25e9fb0e4e0509121342371d925fe5044f8 | https://github.com/ImageMagick/ImageMagick/issues/537 | 0 | static Image *ReadPESImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
char
filename[MagickPathExtent];
FILE
*file;
Image
*image;
ImageInfo
*read_info;
int
delta_x,
delta_y,
j,
unique_file,
x,
y;
MagickBooleanType
status;
PESBlockInfo
block... | 150,432,999,840,845,350,000,000,000,000,000,000,000 | pes.c | 308,145,327,006,151,030,000,000,000,000,000,000,000 | [
"CWE-835"
] | CVE-2017-11446 | The ReadPESImage function in coders\pes.c in ImageMagick 7.0.6-1 has an infinite loop vulnerability that can cause CPU exhaustion via a crafted PES file. | https://nvd.nist.gov/vuln/detail/CVE-2017-11446 |
208,094 | ImageMagick6 | 90401e430840c5ff31ad870f4370bbda1318ac94 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/90401e430840c5ff31ad870f4370bbda1318ac94 | https://github.com/ImageMagick/ImageMagick/issues/1523 | 1 | static MagickBooleanType WritePSImage(const ImageInfo *image_info,Image *image)
{
#define WriteRunlengthPacket(image,pixel,length,p) \
{ \
if ((image->matte != MagickFalse) && (length != 0) &&\
(GetPixelOpacity(p) == (Quantum) TransparentOpacity)) \
{ \
q=PopHexPixel(hex_digits,0xff,q); \
q=PopH... | 83,528,383,458,944,800,000,000,000,000,000,000,000 | ps.c | 337,946,059,615,870,100,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 |
404,997 | ImageMagick6 | 90401e430840c5ff31ad870f4370bbda1318ac94 | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/90401e430840c5ff31ad870f4370bbda1318ac94 | https://github.com/ImageMagick/ImageMagick/issues/1523 | 0 | static MagickBooleanType WritePSImage(const ImageInfo *image_info,Image *image)
{
#define WriteRunlengthPacket(image,pixel,length,p) \
{ \
if ((image->matte != MagickFalse) && (length != 0) &&\
(GetPixelOpacity(p) == (Quantum) TransparentOpacity)) \
{ \
q=PopHexPixel(hex_digits,0xff,q); \
q=PopH... | 306,384,986,189,288,400,000,000,000,000,000,000,000 | ps.c | 80,205,508,495,015,580,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,095 | quagga | a3bc7e9400b214a0f078fdb19596ba54214a1442 | https://github.com/Quagga/quagga | http://git.savannah.gnu.org/cgit/quagga.git/commit/?id=a3bc7e9400b214a0f078fdb19596ba54214a1442 | bgpd: Fix VU#270232, VPNv4 NLRI parser memcpys to stack on unchecked length
Address CERT vulnerability report VU#270232, memcpy to stack data structure
based on length field from packet data whose length field upper-bound was
not properly checked.
This likely allows BGP peers that are enabled to send Labeled-VPN SAFI... | 1 | bgp_nlri_parse_vpnv4 (struct peer *peer, struct attr *attr,
struct bgp_nlri *packet)
{
u_char *pnt;
u_char *lim;
struct prefix p;
int psize;
int prefixlen;
u_int16_t type;
struct rd_as rd_as;
struct rd_ip rd_ip;
struct prefix_rd prd;
u_char *tagpnt;
/* Check peer status. */
if (peer->s... | 114,725,072,160,662,800,000,000,000,000,000,000,000 | bgp_mplsvpn.c | 245,495,823,541,477,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2342 | The bgp_nlri_parse_vpnv4 function in bgp_mplsvpn.c in the VPNv4 NLRI parser in bgpd in Quagga before 1.0.20160309, when a certain VPNv4 configuration is used, relies on a Labeled-VPN SAFI routes-data length field during a data copy, which allows remote attackers to execute arbitrary code or cause a denial of service (s... | https://nvd.nist.gov/vuln/detail/CVE-2016-2342 |
405,015 | quagga | a3bc7e9400b214a0f078fdb19596ba54214a1442 | https://github.com/Quagga/quagga | http://git.savannah.gnu.org/cgit/quagga.git/commit/?id=a3bc7e9400b214a0f078fdb19596ba54214a1442 | bgpd: Fix VU#270232, VPNv4 NLRI parser memcpys to stack on unchecked length
Address CERT vulnerability report VU#270232, memcpy to stack data structure
based on length field from packet data whose length field upper-bound was
not properly checked.
This likely allows BGP peers that are enabled to send Labeled-VPN SAFI... | 0 | bgp_nlri_parse_vpnv4 (struct peer *peer, struct attr *attr,
struct bgp_nlri *packet)
{
u_char *pnt;
u_char *lim;
struct prefix p;
int psize;
int prefixlen;
u_int16_t type;
struct rd_as rd_as;
struct rd_ip rd_ip;
struct prefix_rd prd;
u_char *tagpnt;
/* Check peer status. */
if (peer->s... | 264,439,624,531,550,550,000,000,000,000,000,000,000 | bgp_mplsvpn.c | 142,947,877,026,029,230,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2016-2342 | The bgp_nlri_parse_vpnv4 function in bgp_mplsvpn.c in the VPNv4 NLRI parser in bgpd in Quagga before 1.0.20160309, when a certain VPNv4 configuration is used, relies on a Labeled-VPN SAFI routes-data length field during a data copy, which allows remote attackers to execute arbitrary code or cause a denial of service (s... | https://nvd.nist.gov/vuln/detail/CVE-2016-2342 |
208,096 | ImageMagick | 921f208c2ea3cc45847f380257f270ff424adfff | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/921f208c2ea3cc45847f380257f270ff424adfff | https://github.com/ImageMagick/ImageMagick/issues/1178 | 1 | static Image *ReadDIBImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
DIBInfo
dib_info;
Image
*image;
MagickBooleanType
status;
MemoryInfo
*pixel_info;
Quantum
index;
register ssize_t
x;
register Quantum
*q;
register ssize_t
i;
register unsigned cha... | 28,647,369,001,135,225,000,000,000,000,000,000,000 | dib.c | 326,356,717,369,265,850,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-12600 | In ImageMagick 7.0.8-3 Q16, ReadDIBImage and WriteDIBImage in coders/dib.c allow attackers to cause an out of bounds write via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-12600 |
405,020 | ImageMagick | 921f208c2ea3cc45847f380257f270ff424adfff | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/921f208c2ea3cc45847f380257f270ff424adfff | https://github.com/ImageMagick/ImageMagick/issues/1178 | 0 | static Image *ReadDIBImage(const ImageInfo *image_info,ExceptionInfo *exception)
{
DIBInfo
dib_info;
Image
*image;
MagickBooleanType
status;
MemoryInfo
*pixel_info;
Quantum
index;
register ssize_t
x;
register Quantum
*q;
register ssize_t
i;
register unsigned cha... | 336,050,105,270,863,660,000,000,000,000,000,000,000 | dib.c | 53,349,621,889,029,420,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-12600 | In ImageMagick 7.0.8-3 Q16, ReadDIBImage and WriteDIBImage in coders/dib.c allow attackers to cause an out of bounds write via a crafted file. | https://nvd.nist.gov/vuln/detail/CVE-2018-12600 |
208,106 | ImageMagick6 | 4a8a6274f5e690f9106a998de9b8a8f3929402bc | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/4a8a6274f5e690f9106a998de9b8a8f3929402bc | https://github.com/ImageMagick/ImageMagick/issues/660 | 1 | static int format8BIM(Image *ifile, Image *ofile)
{
char
temp[MaxTextExtent];
unsigned int
foundOSType;
int
ID,
resCount,
i,
c;
ssize_t
count;
unsigned char
*PString,
*str;
resCount=0;
foundOSType=0; /* found the OSType */
(void) foundOSType;
c=ReadBlobByte(ifi... | 136,177,644,572,999,530,000,000,000,000,000,000,000 | meta.c | 134,059,199,002,822,500,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2017-12806 | In ImageMagick 7.0.6-6, a memory exhaustion vulnerability was found in the function format8BIM, which allows attackers to cause a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2017-12806 |
405,323 | ImageMagick6 | 4a8a6274f5e690f9106a998de9b8a8f3929402bc | https://github.com/ImageMagick/ImageMagick6 | https://github.com/ImageMagick/ImageMagick6/commit/4a8a6274f5e690f9106a998de9b8a8f3929402bc | https://github.com/ImageMagick/ImageMagick/issues/660 | 0 | static int format8BIM(Image *ifile, Image *ofile)
{
char
temp[MaxTextExtent];
unsigned int
foundOSType;
int
ID,
resCount,
i,
c;
ssize_t
count;
unsigned char
*PString,
*str;
resCount=0;
foundOSType=0; /* found the OSType */
(void) foundOSType;
c=ReadBlobByte(ifi... | 339,259,270,319,617,460,000,000,000,000,000,000,000 | meta.c | 25,005,859,529,517,887,000,000,000,000,000,000,000 | [
"CWE-400"
] | CVE-2017-12806 | In ImageMagick 7.0.6-6, a memory exhaustion vulnerability was found in the function format8BIM, which allows attackers to cause a denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2017-12806 |
208,109 | liblouis | dbfa58bb128cae86729578ac596056b3385817ef | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/dbfa58bb128cae86729578ac596056b3385817ef | Check index before writing to result->chars
Fixes #595 | 1 | parseChars(FileInfo *nested, CharsString *result, CharsString *token) {
int in = 0;
int out = 0;
int lastOutSize = 0;
int lastIn;
unsigned int ch = 0;
int numBytes = 0;
unsigned int utf32 = 0;
int k;
while (in < token->length) {
ch = token->chars[in++] & 0xff;
if (ch < 128) {
if (ch == '\\') { /* escape... | 100,034,968,813,747,660,000,000,000,000,000,000,000 | compileTranslationTable.c | 207,092,393,170,142,030,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-12085 | Liblouis 3.6.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-12085 |
405,415 | liblouis | dbfa58bb128cae86729578ac596056b3385817ef | https://github.com/liblouis/liblouis | https://github.com/liblouis/liblouis/commit/dbfa58bb128cae86729578ac596056b3385817ef | Check index before writing to result->chars
Fixes #595 | 0 | parseChars(FileInfo *nested, CharsString *result, CharsString *token) {
int in = 0;
int out = 0;
int lastOutSize = 0;
int lastIn;
unsigned int ch = 0;
int numBytes = 0;
unsigned int utf32 = 0;
int k;
while (in < token->length) {
ch = token->chars[in++] & 0xff;
if (ch < 128) {
if (ch == '\\') { /* escape... | 179,517,306,743,897,500,000,000,000,000,000,000,000 | compileTranslationTable.c | 143,489,673,509,276,910,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2018-12085 | Liblouis 3.6.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-12085 |
208,116 | php-src | 75f40ae1f3a7ca837d230f099627d121f9b3a32f | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=75f40ae1f3a7ca837d230f099627d121f9b3a32f | Fixed bug #69293 | 1 | static xmlNodePtr master_to_xml_int(encodePtr encode, zval *data, int style, xmlNodePtr parent, int check_class_map TSRMLS_DC)
{
xmlNodePtr node = NULL;
int add_type = 0;
/* Special handling of class SoapVar */
if (data &&
Z_TYPE_P(data) == IS_OBJECT &&
Z_OBJCE_P(data) == soap_var_class_entry) {
zval *... | 324,236,157,455,624,270,000,000,000,000,000,000,000 | php_encoding.c | 329,270,771,036,043,730,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2015-4147 | The SoapClient::__call method in ext/soap/soap.c in PHP before 5.4.39, 5.5.x before 5.5.23, and 5.6.x before 5.6.7 does not verify that __default_headers is an array, which allows remote attackers to execute arbitrary code by providing crafted serialized data with an unexpected data type, related to a "type confusion" ... | https://nvd.nist.gov/vuln/detail/CVE-2015-4147 |
405,805 | php-src | 75f40ae1f3a7ca837d230f099627d121f9b3a32f | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commit;h=75f40ae1f3a7ca837d230f099627d121f9b3a32f | Fixed bug #69293 | 0 | static xmlNodePtr master_to_xml_int(encodePtr encode, zval *data, int style, xmlNodePtr parent, int check_class_map TSRMLS_DC)
{
xmlNodePtr node = NULL;
int add_type = 0;
/* Special handling of class SoapVar */
if (data &&
Z_TYPE_P(data) == IS_OBJECT &&
Z_OBJCE_P(data) == soap_var_class_entry) {
zval *... | 91,269,179,654,001,640,000,000,000,000,000,000,000 | php_encoding.c | 61,107,141,967,899,740,000,000,000,000,000,000,000 | [
"CWE-19"
] | CVE-2015-4147 | The SoapClient::__call method in ext/soap/soap.c in PHP before 5.4.39, 5.5.x before 5.5.23, and 5.6.x before 5.6.7 does not verify that __default_headers is an array, which allows remote attackers to execute arbitrary code by providing crafted serialized data with an unexpected data type, related to a "type confusion" ... | https://nvd.nist.gov/vuln/detail/CVE-2015-4147 |
208,117 | thunar | 03dd312e157d4fa8a11d5fa402706ae5b05806fa | https://github.com/xfce-mirror/thunar | https://github.com/xfce-mirror/thunar/commit/03dd312e157d4fa8a11d5fa402706ae5b05806fa | Don't interpret file display names as format strings
This avoids a segfault when copying/moving files containing "%" formatters
in their name.
Signed-off-by: Jannis Pohlmann <jannis@xfce.org> | 1 | thunar_transfer_job_copy_node (ThunarTransferJob *job,
ThunarTransferNode *node,
GFile *target_file,
GFile *target_parent_file,
GList **target_file_list_retu... | 67,032,922,566,912,730,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2011-1588 | Thunar before 1.3.1 could crash when copy and pasting a file name with % format characters due to a format string error. | https://nvd.nist.gov/vuln/detail/CVE-2011-1588 |
405,806 | thunar | 03dd312e157d4fa8a11d5fa402706ae5b05806fa | https://github.com/xfce-mirror/thunar | https://github.com/xfce-mirror/thunar/commit/03dd312e157d4fa8a11d5fa402706ae5b05806fa | Don't interpret file display names as format strings
This avoids a segfault when copying/moving files containing "%" formatters
in their name.
Signed-off-by: Jannis Pohlmann <jannis@xfce.org> | 0 | thunar_transfer_job_copy_node (ThunarTransferJob *job,
ThunarTransferNode *node,
GFile *target_file,
GFile *target_parent_file,
GList **target_file_list_retu... | 51,971,119,470,506,470,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2011-1588 | Thunar before 1.3.1 could crash when copy and pasting a file name with % format characters due to a format string error. | https://nvd.nist.gov/vuln/detail/CVE-2011-1588 |
208,126 | linux | 0cbb4b4f4c44f54af268969b18d8deda63aded59 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0cbb4b4f4c44f54af268969b18d8deda63aded59 | userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK fails
The previous fix in commit 384632e67e08 ("userfaultfd: non-cooperative:
fix fork use after free") corrected the refcounting in case of
UFFD_EVENT_FORK failure for the fork userfault paths.
That still didn't clear the vma->vm_userfaultfd_ctx of th... | 1 | static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,
struct userfaultfd_wait_queue *ewq)
{
if (WARN_ON_ONCE(current->flags & PF_EXITING))
goto out;
ewq->ctx = ctx;
init_waitqueue_entry(&ewq->wq, current);
spin_lock(&ctx->event_wqh.lock);
/*
* After the __add_wait_queue the uw... | 292,462,795,966,210,350,000,000,000,000,000,000,000 | userfaultfd.c | 237,936,217,023,476,630,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15126 | A use-after-free flaw was found in fs/userfaultfd.c in the Linux kernel before 4.13.6. The issue is related to the handling of fork failure when dealing with event messages. Failure to fork correctly can lead to a situation where a fork event will be removed from an already freed list of events with userfaultfd_ctx_put... | https://nvd.nist.gov/vuln/detail/CVE-2017-15126 |
405,900 | linux | 0cbb4b4f4c44f54af268969b18d8deda63aded59 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0cbb4b4f4c44f54af268969b18d8deda63aded59 | userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK fails
The previous fix in commit 384632e67e08 ("userfaultfd: non-cooperative:
fix fork use after free") corrected the refcounting in case of
UFFD_EVENT_FORK failure for the fork userfault paths.
That still didn't clear the vma->vm_userfaultfd_ctx of th... | 0 | static void userfaultfd_event_wait_completion(struct userfaultfd_ctx *ctx,
struct userfaultfd_wait_queue *ewq)
{
struct userfaultfd_ctx *release_new_ctx;
if (WARN_ON_ONCE(current->flags & PF_EXITING))
goto out;
ewq->ctx = ctx;
init_waitqueue_entry(&ewq->wq, current);
release_new_ctx = NULL;
spin_l... | 258,318,050,357,376,520,000,000,000,000,000,000,000 | userfaultfd.c | 147,018,184,534,711,540,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-15126 | A use-after-free flaw was found in fs/userfaultfd.c in the Linux kernel before 4.13.6. The issue is related to the handling of fork failure when dealing with event messages. Failure to fork correctly can lead to a situation where a fork event will be removed from an already freed list of events with userfaultfd_ctx_put... | https://nvd.nist.gov/vuln/detail/CVE-2017-15126 |
208,139 | linux | 9a59b62fd88196844cee5fff851bee2cfd7afb6e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9a59b62fd88196844cee5fff851bee2cfd7afb6e | f2fs: do more integrity verification for superblock
Do more sanity check for superblock during ->mount.
Signed-off-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> | 1 | static int sanity_check_raw_super(struct super_block *sb,
struct f2fs_super_block *raw_super)
{
unsigned int blocksize;
if (F2FS_SUPER_MAGIC != le32_to_cpu(raw_super->magic)) {
f2fs_msg(sb, KERN_INFO,
"Magic Mismatch, valid(0x%x) - read(0x%x)",
F2FS_SUPER_MAGIC, le32_to_cpu(raw_super->magic));
return 1;... | 116,149,217,992,963,250,000,000,000,000,000,000,000 | super.c | 251,528,749,519,773,960,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-0750 | A elevation of privilege vulnerability in the Upstream Linux file system. Product: Android. Versions: Android kernel. Android ID: A-36817013. | https://nvd.nist.gov/vuln/detail/CVE-2017-0750 |
406,176 | linux | 9a59b62fd88196844cee5fff851bee2cfd7afb6e | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9a59b62fd88196844cee5fff851bee2cfd7afb6e | f2fs: do more integrity verification for superblock
Do more sanity check for superblock during ->mount.
Signed-off-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org> | 0 | static int sanity_check_raw_super(struct super_block *sb,
struct f2fs_super_block *raw_super)
{
unsigned int blocksize;
if (F2FS_SUPER_MAGIC != le32_to_cpu(raw_super->magic)) {
f2fs_msg(sb, KERN_INFO,
"Magic Mismatch, valid(0x%x) - read(0x%x)",
F2FS_SUPER_MAGIC, le32_to_cpu(raw_super->magic));
return 1;... | 128,260,968,931,316,400,000,000,000,000,000,000,000 | super.c | 335,452,887,018,590,730,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2017-0750 | A elevation of privilege vulnerability in the Upstream Linux file system. Product: Android. Versions: Android kernel. Android ID: A-36817013. | https://nvd.nist.gov/vuln/detail/CVE-2017-0750 |
208,165 | advancecomp | 78a56b21340157775be2462a19276b4d31d2bd01 | https://github.com/amadvance/advancecomp | https://github.com/amadvance/advancecomp/commit/78a56b21340157775be2462a19276b4d31d2bd01 | Fix a buffer overflow caused by invalid images | 1 | adv_error adv_png_read_ihdr(
unsigned* pix_width, unsigned* pix_height, unsigned* pix_pixel,
unsigned char** dat_ptr, unsigned* dat_size,
unsigned char** pix_ptr, unsigned* pix_scanline,
unsigned char** pal_ptr, unsigned* pal_size,
unsigned char** rns_ptr, unsigned* rns_size,
adv_fz* f, const unsigned char* data,... | 23,277,060,438,988,170,000,000,000,000,000,000,000 | png.c | 309,199,410,137,273,600,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2019-8383 | An issue was discovered in AdvanceCOMP through 2.1. An invalid memory address occurs in the function adv_png_unfilter_8 in lib/png.c. It can be triggered by sending a crafted file to a binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact when a victim... | https://nvd.nist.gov/vuln/detail/CVE-2019-8383 |
406,366 | advancecomp | 78a56b21340157775be2462a19276b4d31d2bd01 | https://github.com/amadvance/advancecomp | https://github.com/amadvance/advancecomp/commit/78a56b21340157775be2462a19276b4d31d2bd01 | Fix a buffer overflow caused by invalid images | 0 | adv_error adv_png_read_ihdr(
unsigned* pix_width, unsigned* pix_height, unsigned* pix_pixel,
unsigned char** dat_ptr, unsigned* dat_size,
unsigned char** pix_ptr, unsigned* pix_scanline,
unsigned char** pal_ptr, unsigned* pal_size,
unsigned char** rns_ptr, unsigned* rns_size,
adv_fz* f, const unsigned char* data,... | 184,685,119,959,434,970,000,000,000,000,000,000,000 | png.c | 206,312,328,085,819,860,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2019-8383 | An issue was discovered in AdvanceCOMP through 2.1. An invalid memory address occurs in the function adv_png_unfilter_8 in lib/png.c. It can be triggered by sending a crafted file to a binary. It allows an attacker to cause a Denial of Service (Segmentation fault) or possibly have unspecified other impact when a victim... | https://nvd.nist.gov/vuln/detail/CVE-2019-8383 |
208,167 | openjpeg | 4241ae6fbbf1de9658764a80944dc8108f2b4154 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/4241ae6fbbf1de9658764a80944dc8108f2b4154 | Fix assertion in debug mode / heap-based buffer overflow in opj_write_bytes_LE for Cinema profiles with numresolutions = 1 (#985) | 1 | static void opj_j2k_set_cinema_parameters(opj_cparameters_t *parameters,
opj_image_t *image, opj_event_mgr_t *p_manager)
{
/* Configure cinema parameters */
int i;
/* No tiling */
parameters->tile_size_on = OPJ_FALSE;
parameters->cp_tdx = 1;
parameters->cp_tdy = 1;
/* One tile part... | 194,523,386,640,950,100,000,000,000,000,000,000,000 | j2k.c | 217,457,036,836,182,600,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-14152 | A mishandled zero case was discovered in opj_j2k_set_cinema_parameters in lib/openjp2/j2k.c in OpenJPEG 2.2.0. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service (heap-based buffer overflow affecting opj_write_bytes_LE in lib/openjp2/cio.c and opj_j2k_write_sot in lib/openjp2/j2... | https://nvd.nist.gov/vuln/detail/CVE-2017-14152 |
406,386 | openjpeg | 4241ae6fbbf1de9658764a80944dc8108f2b4154 | https://github.com/uclouvain/openjpeg | https://github.com/uclouvain/openjpeg/commit/4241ae6fbbf1de9658764a80944dc8108f2b4154 | Fix assertion in debug mode / heap-based buffer overflow in opj_write_bytes_LE for Cinema profiles with numresolutions = 1 (#985) | 0 | static void opj_j2k_set_cinema_parameters(opj_cparameters_t *parameters,
opj_image_t *image, opj_event_mgr_t *p_manager)
{
/* Configure cinema parameters */
int i;
/* No tiling */
parameters->tile_size_on = OPJ_FALSE;
parameters->cp_tdx = 1;
parameters->cp_tdy = 1;
/* One tile part... | 207,136,894,911,227,720,000,000,000,000,000,000,000 | j2k.c | 255,046,900,097,724,900,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2017-14152 | A mishandled zero case was discovered in opj_j2k_set_cinema_parameters in lib/openjp2/j2k.c in OpenJPEG 2.2.0. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service (heap-based buffer overflow affecting opj_write_bytes_LE in lib/openjp2/cio.c and opj_j2k_write_sot in lib/openjp2/j2... | https://nvd.nist.gov/vuln/detail/CVE-2017-14152 |
208,168 | ImageMagick | 4ab4849d667e26df0e63ece9d63ae23bc7ab0fa1 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4ab4849d667e26df0e63ece9d63ae23bc7ab0fa1 | https://github.com/ImageMagick/ImageMagick/issues/1195 | 1 | static Image *XMagickCommand(Display *display,XResourceInfo *resource_info,
XWindows *windows,const CommandType command_type,Image **image,
MagickStatusType *state,ExceptionInfo *exception)
{
Image
*nexus;
MagickBooleanType
proceed;
MagickStatusType
status;
XTextProperty
window_name;
/... | 283,634,253,432,778,150,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2018-13153 | In ImageMagick 7.0.8-4, there is a memory leak in the XMagickCommand function in MagickCore/animate.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-13153 |
406,413 | ImageMagick | 4ab4849d667e26df0e63ece9d63ae23bc7ab0fa1 | https://github.com/ImageMagick/ImageMagick | https://github.com/ImageMagick/ImageMagick/commit/4ab4849d667e26df0e63ece9d63ae23bc7ab0fa1 | https://github.com/ImageMagick/ImageMagick/issues/1195 | 0 | static Image *XMagickCommand(Display *display,XResourceInfo *resource_info,
XWindows *windows,const CommandType command_type,Image **image,
MagickStatusType *state,ExceptionInfo *exception)
{
Image
*nexus;
MagickBooleanType
proceed;
MagickStatusType
status;
XTextProperty
window_name;
/... | 23,858,936,328,586,210,000,000,000,000,000,000,000 | None | null | [
"CWE-772"
] | CVE-2018-13153 | In ImageMagick 7.0.8-4, there is a memory leak in the XMagickCommand function in MagickCore/animate.c. | https://nvd.nist.gov/vuln/detail/CVE-2018-13153 |
208,187 | php-src | ed6dee9a198c904ad5e03113e58a2d2c200f5184 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=ed6dee9a198c904ad5e03113e58a2d2c200f5184 | Fix #77973: Uninitialized read in gdImageCreateFromXbm
We have to ensure that `sscanf()` does indeed read a hex value here,
and bail out otherwise. | 1 | gdImagePtr gdImageCreateFromXbm(FILE * fd)
{
char fline[MAX_XBM_LINE_SIZE];
char iname[MAX_XBM_LINE_SIZE];
char *type;
int value;
unsigned int width = 0, height = 0;
int fail = 0;
int max_bit = 0;
gdImagePtr im;
int bytes = 0, i;
int bit, x = 0, y = 0;
int ch;
char h[8];
unsigned int b;
rewind(fd);
whi... | 100,849,927,989,583,500,000,000,000,000,000,000,000 | xbm.c | 36,922,797,505,809,220,000,000,000,000,000,000,000 | [
"CWE-908"
] | CVE-2019-11038 | When using the gdImageCreateFromXbm() function in the GD Graphics Library (aka LibGD) 2.2.5, as used in the PHP GD extension in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6, it is possible to supply data that will cause the function to use the value of uninitialized variable. This may lead ... | https://nvd.nist.gov/vuln/detail/CVE-2019-11038 |
406,509 | php-src | ed6dee9a198c904ad5e03113e58a2d2c200f5184 | https://github.com/php/php-src | http://git.php.net/?p=php-src.git;a=commitdiff;h=ed6dee9a198c904ad5e03113e58a2d2c200f5184 | Fix #77973: Uninitialized read in gdImageCreateFromXbm
We have to ensure that `sscanf()` does indeed read a hex value here,
and bail out otherwise. | 0 | gdImagePtr gdImageCreateFromXbm(FILE * fd)
{
char fline[MAX_XBM_LINE_SIZE];
char iname[MAX_XBM_LINE_SIZE];
char *type;
int value;
unsigned int width = 0, height = 0;
int fail = 0;
int max_bit = 0;
gdImagePtr im;
int bytes = 0, i;
int bit, x = 0, y = 0;
int ch;
char h[8];
unsigned int b;
rewind(fd);
whi... | 332,545,135,573,057,500,000,000,000,000,000,000,000 | xbm.c | 6,868,434,290,304,716,000,000,000,000,000,000,000 | [
"CWE-908"
] | CVE-2019-11038 | When using the gdImageCreateFromXbm() function in the GD Graphics Library (aka LibGD) 2.2.5, as used in the PHP GD extension in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6, it is possible to supply data that will cause the function to use the value of uninitialized variable. This may lead ... | https://nvd.nist.gov/vuln/detail/CVE-2019-11038 |
208,190 | Sigil | 0979ba8d10c96ebca330715bfd4494ea0e019a8f | https://github.com/Sigil-Ebook/Sigil | https://github.com/Sigil-Ebook/Sigil/commit/0979ba8d10c96ebca330715bfd4494ea0e019a8f | harden plugin unzipping to zip-slip attacks | 1 | bool Utility::UnZip(const QString &zippath, const QString &destpath)
{
int res = 0;
QDir dir(destpath);
if (!cp437) {
cp437 = new QCodePage437Codec();
}
#ifdef Q_OS_WIN32
zlib_filefunc64_def ffunc;
fill_win32_filefunc64W(&ffunc);
unzFile zfile = unzOpen2_64(Utility::QStringToStdWStri... | 9,061,989,152,897,669,000,000,000,000,000,000,000 | Utility.cpp | 178,718,781,997,101,280,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2019-14452 | Sigil before 0.9.16 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in a ZIP archive entry that is mishandled during extraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-14452 |
406,629 | Sigil | 0979ba8d10c96ebca330715bfd4494ea0e019a8f | https://github.com/Sigil-Ebook/Sigil | https://github.com/Sigil-Ebook/Sigil/commit/0979ba8d10c96ebca330715bfd4494ea0e019a8f | harden plugin unzipping to zip-slip attacks | 0 | bool Utility::UnZip(const QString &zippath, const QString &destpath)
{
int res = 0;
QDir dir(destpath);
if (!cp437) {
cp437 = new QCodePage437Codec();
}
#ifdef Q_OS_WIN32
zlib_filefunc64_def ffunc;
fill_win32_filefunc64W(&ffunc);
unzFile zfile = unzOpen2_64(Utility::QStringToStdWStri... | 252,925,947,740,982,120,000,000,000,000,000,000,000 | Utility.cpp | 236,631,074,199,918,050,000,000,000,000,000,000,000 | [
"CWE-22"
] | CVE-2019-14452 | Sigil before 0.9.16 is vulnerable to a directory traversal, allowing attackers to write arbitrary files via a ../ (dot dot slash) in a ZIP archive entry that is mishandled during extraction. | https://nvd.nist.gov/vuln/detail/CVE-2019-14452 |
208,191 | linux | 57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581 | net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
ax88179_rx_fixup() contains several out-of-bounds accesses that can be
triggered by a malicious (or defective) USB device, in particular:
- The metadata array (hdr_off..hdr_off+2*pkt_cnt) can be out of bounds,
causing OOB reads and (on big-endian syst... | 1 | static int ax88179_rx_fixup(struct usbnet *dev, struct sk_buff *skb)
{
struct sk_buff *ax_skb;
int pkt_cnt;
u32 rx_hdr;
u16 hdr_off;
u32 *pkt_hdr;
/* This check is no longer done by usbnet */
if (skb->len < dev->net->hard_header_len)
return 0;
skb_trim(skb, skb->len - 4);
rx_hdr = get_unaligned_le32(skb_ta... | 164,637,807,638,425,500,000,000,000,000,000,000,000 | ax88179_178a.c | 66,770,514,852,203,995,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2022-2964 | A flaw was found in the Linux kernel’s driver for the ASIX AX88179_178A-based USB 2.0/3.0 Gigabit Ethernet Devices. The vulnerability contains multiple out-of-bounds reads and possible out-of-bounds writes. | https://nvd.nist.gov/vuln/detail/CVE-2022-2964 |
406,641 | linux | 57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57bc3d3ae8c14df3ceb4e17d26ddf9eeab304581 | net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
ax88179_rx_fixup() contains several out-of-bounds accesses that can be
triggered by a malicious (or defective) USB device, in particular:
- The metadata array (hdr_off..hdr_off+2*pkt_cnt) can be out of bounds,
causing OOB reads and (on big-endian syst... | 0 | static int ax88179_rx_fixup(struct usbnet *dev, struct sk_buff *skb)
{
struct sk_buff *ax_skb;
int pkt_cnt;
u32 rx_hdr;
u16 hdr_off;
u32 *pkt_hdr;
/* At the end of the SKB, there's a header telling us how many packets
* are bundled into this buffer and where we can find an array of
* per-packet metadata (whi... | 32,798,802,816,716,414,000,000,000,000,000,000,000 | ax88179_178a.c | 190,843,260,678,446,560,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2022-2964 | A flaw was found in the Linux kernel’s driver for the ASIX AX88179_178A-based USB 2.0/3.0 Gigabit Ethernet Devices. The vulnerability contains multiple out-of-bounds reads and possible out-of-bounds writes. | https://nvd.nist.gov/vuln/detail/CVE-2022-2964 |
208,194 | gnutls | 7429872b74c8216bbf15e241e47aba94369ef083 | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/7429872b74c8216bbf15e241e47aba94369ef083 | when exporting curve coordinates to X9.63 format, perform additional sanity checks on input
Reported by Sean Burford. | 1 | _gnutls_ecc_ansi_x963_export (gnutls_ecc_curve_t curve, bigint_t x, bigint_t y,
gnutls_datum_t * out)
{
int numlen = gnutls_ecc_curve_get_size (curve);
int byte_size, ret;
size_t size;
if (numlen == 0)
return gnutls_assert_val (GNUTLS_E_INVALID_REQUEST);
out->size = 1 + 2 *... | 77,733,135,364,757,890,000,000,000,000,000,000,000 | gnutls_ecc.c | 184,010,150,535,098,630,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2014-8564 | The _gnutls_ecc_ansi_x963_export function in gnutls_ecc.c in GnuTLS 3.x before 3.1.28, 3.2.x before 3.2.20, and 3.3.x before 3.3.10 allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted (1) Elliptic Curve Cryptography (ECC) certificate or (2) certificate signing requests (CSR), relate... | https://nvd.nist.gov/vuln/detail/CVE-2014-8564 |
406,684 | gnutls | 7429872b74c8216bbf15e241e47aba94369ef083 | http://git.savannah.gnu.org/cgit/gnutls | https://gitorious.org/gnutls/gnutls/commit/7429872b74c8216bbf15e241e47aba94369ef083 | when exporting curve coordinates to X9.63 format, perform additional sanity checks on input
Reported by Sean Burford. | 0 | _gnutls_ecc_ansi_x963_export (gnutls_ecc_curve_t curve, bigint_t x, bigint_t y,
gnutls_datum_t * out)
{
int numlen = gnutls_ecc_curve_get_size (curve);
int byte_size, ret;
size_t size;
if (numlen == 0)
return gnutls_assert_val (GNUTLS_E_INVALID_REQUEST);
out->size = 1 + 2 *... | 199,843,810,686,047,500,000,000,000,000,000,000,000 | gnutls_ecc.c | 232,699,558,835,122,350,000,000,000,000,000,000,000 | [
"CWE-310"
] | CVE-2014-8564 | The _gnutls_ecc_ansi_x963_export function in gnutls_ecc.c in GnuTLS 3.x before 3.1.28, 3.2.x before 3.2.20, and 3.3.x before 3.3.10 allows remote attackers to cause a denial of service (out-of-bounds write) via a crafted (1) Elliptic Curve Cryptography (ECC) certificate or (2) certificate signing requests (CSR), relate... | https://nvd.nist.gov/vuln/detail/CVE-2014-8564 |
208,195 | heimdal | 6dd3eb836bbb80a00ffced4ad57077a1cdf227ea | https://github.com/heimdal/heimdal | https://github.com/heimdal/heimdal/commit/6dd3eb836bbb80a00ffced4ad57077a1cdf227ea | CVE-2017-11103: Orpheus' Lyre KDC-REP service name validation
In _krb5_extract_ticket() the KDC-REP service name must be obtained from
encrypted version stored in 'enc_part' instead of the unencrypted version
stored in 'ticket'. Use of the unecrypted version provides an
opportunity for successful server impersonation... | 1 | _krb5_extract_ticket(krb5_context context,
krb5_kdc_rep *rep,
krb5_creds *creds,
krb5_keyblock *key,
krb5_const_pointer keyseed,
krb5_key_usage key_usage,
krb5_addresses *addrs,
unsigned nonce,
unsigned flags,
krb5_data *request,
krb5_decrypt_proc de... | 75,153,775,144,300,680,000,000,000,000,000,000,000 | ticket.c | 67,753,007,531,853,500,000,000,000,000,000,000,000 | [
"CWE-345"
] | CVE-2017-11103 | Heimdal before 7.4 allows remote attackers to impersonate services with Orpheus' Lyre attacks because it obtains service-principal names in a way that violates the Kerberos 5 protocol specification. In _krb5_extract_ticket() the KDC-REP service name must be obtained from the encrypted version stored in 'enc_part' inste... | https://nvd.nist.gov/vuln/detail/CVE-2017-11103 |
406,694 | heimdal | 6dd3eb836bbb80a00ffced4ad57077a1cdf227ea | https://github.com/heimdal/heimdal | https://github.com/heimdal/heimdal/commit/6dd3eb836bbb80a00ffced4ad57077a1cdf227ea | CVE-2017-11103: Orpheus' Lyre KDC-REP service name validation
In _krb5_extract_ticket() the KDC-REP service name must be obtained from
encrypted version stored in 'enc_part' instead of the unencrypted version
stored in 'ticket'. Use of the unecrypted version provides an
opportunity for successful server impersonation... | 0 | _krb5_extract_ticket(krb5_context context,
krb5_kdc_rep *rep,
krb5_creds *creds,
krb5_keyblock *key,
krb5_const_pointer keyseed,
krb5_key_usage key_usage,
krb5_addresses *addrs,
unsigned nonce,
unsigned flags,
krb5_data *request,
krb5_decrypt_proc de... | 176,253,040,766,340,860,000,000,000,000,000,000,000 | ticket.c | 44,591,451,656,181,200,000,000,000,000,000,000,000 | [
"CWE-345"
] | CVE-2017-11103 | Heimdal before 7.4 allows remote attackers to impersonate services with Orpheus' Lyre attacks because it obtains service-principal names in a way that violates the Kerberos 5 protocol specification. In _krb5_extract_ticket() the KDC-REP service name must be obtained from the encrypted version stored in 'enc_part' inste... | https://nvd.nist.gov/vuln/detail/CVE-2017-11103 |
208,196 | linux | 17839856fd588f4ab6b789f482ed3ffd7c403e1f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17839856fd588f4ab6b789f482ed3ffd7c403e1f | gup: document and work around "COW can break either way" issue
Doing a "get_user_pages()" on a copy-on-write page for reading can be
ambiguous: the page can be COW'ed at any time afterwards, and the
direction of a COW event isn't defined.
Yes, whoever writes to it will generally do the COW, but if the thread
that did... | 1 | static inline bool can_follow_write_pmd(pmd_t pmd, unsigned int flags)
{
return pmd_write(pmd) ||
((flags & FOLL_FORCE) && (flags & FOLL_COW) && pmd_dirty(pmd));
} | 81,158,621,214,781,275,000,000,000,000,000,000,000 | huge_memory.c | 142,804,299,309,607,250,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2020-29374 | An issue was discovered in the Linux kernel before 5.7.3, related to mm/gup.c and mm/huge_memory.c. The get_user_pages (aka gup) implementation, when used for a copy-on-write page, does not properly consider the semantics of read operations and therefore can grant unintended write access, aka CID-17839856fd58. | https://nvd.nist.gov/vuln/detail/CVE-2020-29374 |
406,736 | linux | 17839856fd588f4ab6b789f482ed3ffd7c403e1f | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17839856fd588f4ab6b789f482ed3ffd7c403e1f | gup: document and work around "COW can break either way" issue
Doing a "get_user_pages()" on a copy-on-write page for reading can be
ambiguous: the page can be COW'ed at any time afterwards, and the
direction of a COW event isn't defined.
Yes, whoever writes to it will generally do the COW, but if the thread
that did... | 0 | static inline bool can_follow_write_pte(pte_t pte, unsigned int flags)
{
return pte_write(pte) || ((flags & FOLL_COW) && pte_dirty(pte));
} | 27,376,554,165,339,220,000,000,000,000,000,000,000 | gup.c | 241,548,885,084,044,230,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2020-29374 | An issue was discovered in the Linux kernel before 5.7.3, related to mm/gup.c and mm/huge_memory.c. The get_user_pages (aka gup) implementation, when used for a copy-on-write page, does not properly consider the semantics of read operations and therefore can grant unintended write access, aka CID-17839856fd58. | https://nvd.nist.gov/vuln/detail/CVE-2020-29374 |
208,204 | linux | c666355e60ddb4748ead3bdd983e3f7f2224aaf0 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c666355e60ddb4748ead3bdd983e3f7f2224aaf0 | media: radio-raremono: change devm_k*alloc to k*alloc
Change devm_k*alloc to k*alloc to manually allocate memory
The manual allocation and freeing of memory is necessary because when
the USB radio is disconnected, the memory associated with devm_k*alloc
is freed. Meaning if we still have unresolved references to the ... | 1 | static int usb_raremono_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct raremono_device *radio;
int retval = 0;
radio = devm_kzalloc(&intf->dev, sizeof(struct raremono_device), GFP_KERNEL);
if (radio)
radio->buffer = devm_kmalloc(&intf->dev, BUFFER_LENGTH, GFP_KERNEL);
if (!radio... | 301,752,479,975,448,170,000,000,000,000,000,000,000 | radio-raremono.c | 325,564,844,597,447,700,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15211 | An issue was discovered in the Linux kernel before 5.2.6. There is a use-after-free caused by a malicious USB device in the drivers/media/v4l2-core/v4l2-dev.c driver because drivers/media/radio/radio-raremono.c does not properly allocate memory. | https://nvd.nist.gov/vuln/detail/CVE-2019-15211 |
406,864 | linux | c666355e60ddb4748ead3bdd983e3f7f2224aaf0 | https://github.com/torvalds/linux | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c666355e60ddb4748ead3bdd983e3f7f2224aaf0 | media: radio-raremono: change devm_k*alloc to k*alloc
Change devm_k*alloc to k*alloc to manually allocate memory
The manual allocation and freeing of memory is necessary because when
the USB radio is disconnected, the memory associated with devm_k*alloc
is freed. Meaning if we still have unresolved references to the ... | 0 | static int usb_raremono_probe(struct usb_interface *intf,
const struct usb_device_id *id)
{
struct raremono_device *radio;
int retval = 0;
radio = kzalloc(sizeof(*radio), GFP_KERNEL);
if (!radio)
return -ENOMEM;
radio->buffer = kmalloc(BUFFER_LENGTH, GFP_KERNEL);
if (!radio->buffer) {
kfree(radio);
ret... | 148,411,792,160,036,470,000,000,000,000,000,000,000 | radio-raremono.c | 206,567,293,223,524,230,000,000,000,000,000,000,000 | [
"CWE-416"
] | CVE-2019-15211 | An issue was discovered in the Linux kernel before 5.2.6. There is a use-after-free caused by a malicious USB device in the drivers/media/v4l2-core/v4l2-dev.c driver because drivers/media/radio/radio-raremono.c does not properly allocate memory. | https://nvd.nist.gov/vuln/detail/CVE-2019-15211 |
208,227 | openexr | 85fd638ae0d5fa132434f4cbf32590261c1dba97 | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/85fd638ae0d5fa132434f4cbf32590261c1dba97 | reduce B44 _tmpBufferSize (was allocating two bytes per byte) (#843)
Signed-off-by: Peter Hillman <peterh@wetafx.co.nz> | 1 | B44Compressor::B44Compressor
(const Header &hdr,
size_t maxScanLineSize,
size_t numScanLines,
bool optFlatFields)
:
Compressor (hdr),
_maxScanLineSize (maxScanLineSize),
_optFlatFields (optFlatFields),
_format (XDR),
_numScanLines (numScanLines),
_tmpBuffer (0),
_outBuffer... | 264,368,506,590,496,160,000,000,000,000,000,000,000 | ImfB44Compressor.cpp | 85,648,547,173,206,680,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-20298 | A flaw was found in OpenEXR's B44Compressor. This flaw allows an attacker who can submit a crafted file to be processed by OpenEXR, to exhaust all memory accessible to the application. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20298 |
406,984 | openexr | 85fd638ae0d5fa132434f4cbf32590261c1dba97 | https://github.com/AcademySoftwareFoundation/openexr | https://github.com/AcademySoftwareFoundation/openexr/commit/85fd638ae0d5fa132434f4cbf32590261c1dba97 | reduce B44 _tmpBufferSize (was allocating two bytes per byte) (#843)
Signed-off-by: Peter Hillman <peterh@wetafx.co.nz> | 0 | B44Compressor::B44Compressor
(const Header &hdr,
size_t maxScanLineSize,
size_t numScanLines,
bool optFlatFields)
:
Compressor (hdr),
_maxScanLineSize (maxScanLineSize),
_optFlatFields (optFlatFields),
_format (XDR),
_numScanLines (numScanLines),
_tmpBuffer (0),
_outBuffer... | 142,838,828,004,078,450,000,000,000,000,000,000,000 | ImfB44Compressor.cpp | 316,194,742,477,896,140,000,000,000,000,000,000,000 | [
"CWE-787"
] | CVE-2021-20298 | A flaw was found in OpenEXR's B44Compressor. This flaw allows an attacker who can submit a crafted file to be processed by OpenEXR, to exhaust all memory accessible to the application. The highest threat from this vulnerability is to system availability. | https://nvd.nist.gov/vuln/detail/CVE-2021-20298 |
208,248 | linux-fbdev | 15cf0b82271b1823fb02ab8c377badba614d95d5 | https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev | https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/commit/?id=15cf0b82271b1823fb02ab8c377badba614d95d5 | video: fbdev: i740fb: Error out if 'pixclock' equals zero
The userspace program could pass any values to the driver through
ioctl() interface. If the driver doesn't check the value of 'pixclock',
it may cause divide error.
Fix this by checking whether 'pixclock' is zero in the function
i740fb_check_var().
The follow... | 1 | static int i740fb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
{
switch (var->bits_per_pixel) {
case 8:
var->red.offset = var->green.offset = var->blue.offset = 0;
var->red.length = var->green.length = var->blue.length = 8;
break;
case 16:
switch (var->green.length) {
default:
case 5:
... | 285,486,311,177,820,850,000,000,000,000,000,000,000 | i740fb.c | 144,686,508,874,935,860,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2022-3061 | Found Linux Kernel flaw in the i740 driver. The Userspace program could pass any values to the driver through ioctl() interface. The driver doesn't check the value of 'pixclock', so it may cause a divide by zero error. | https://nvd.nist.gov/vuln/detail/CVE-2022-3061 |
407,688 | linux-fbdev | 15cf0b82271b1823fb02ab8c377badba614d95d5 | https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev | https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/commit/?id=15cf0b82271b1823fb02ab8c377badba614d95d5 | video: fbdev: i740fb: Error out if 'pixclock' equals zero
The userspace program could pass any values to the driver through
ioctl() interface. If the driver doesn't check the value of 'pixclock',
it may cause divide error.
Fix this by checking whether 'pixclock' is zero in the function
i740fb_check_var().
The follow... | 0 | static int i740fb_check_var(struct fb_var_screeninfo *var, struct fb_info *info)
{
if (!var->pixclock)
return -EINVAL;
switch (var->bits_per_pixel) {
case 8:
var->red.offset = var->green.offset = var->blue.offset = 0;
var->red.length = var->green.length = var->blue.length = 8;
break;
case 16:
switch (var... | 143,612,926,213,857,550,000,000,000,000,000,000,000 | i740fb.c | 8,460,928,768,881,982,000,000,000,000,000,000,000 | [
"CWE-369"
] | CVE-2022-3061 | Found Linux Kernel flaw in the i740 driver. The Userspace program could pass any values to the driver through ioctl() interface. The driver doesn't check the value of 'pixclock', so it may cause a divide by zero error. | https://nvd.nist.gov/vuln/detail/CVE-2022-3061 |
208,253 | linux | f2e5ddcc0d12f9c4c7b254358ad245c9dddce13b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f2e5ddcc0d12f9c4c7b254358ad245c9dddce13b | net: fix cipso packet validation when !NETLABEL
When CONFIG_NETLABEL is disabled, the cipso_v4_validate() function could loop
forever in the main loop if opt[opt_iter +1] == 0, this will causing a kernel
crash in an SMP system, since the CPU executing this function will
stall /not respond to IPIs.
This problem can be... | 1 | static inline int cipso_v4_validate(const struct sk_buff *skb,
unsigned char **option)
{
unsigned char *opt = *option;
unsigned char err_offset = 0;
u8 opt_len = opt[1];
u8 opt_iter;
if (opt_len < 8) {
err_offset = 1;
goto out;
}
if (get_unaligned_be32(&opt[2]) == 0) {
err_offset = 2;
goto out;... | 326,028,759,862,627,740,000,000,000,000,000,000,000 | cipso_ipv4.h | 74,022,840,407,535,135,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-7470 | cipso_v4_validate in include/net/cipso_ipv4.h in the Linux kernel before 3.11.7, when CONFIG_NETLABEL is disabled, allows attackers to cause a denial of service (infinite loop and crash), as demonstrated by icmpsic, a different vulnerability than CVE-2013-0310. | https://nvd.nist.gov/vuln/detail/CVE-2013-7470 |
407,975 | linux | f2e5ddcc0d12f9c4c7b254358ad245c9dddce13b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f2e5ddcc0d12f9c4c7b254358ad245c9dddce13b | net: fix cipso packet validation when !NETLABEL
When CONFIG_NETLABEL is disabled, the cipso_v4_validate() function could loop
forever in the main loop if opt[opt_iter +1] == 0, this will causing a kernel
crash in an SMP system, since the CPU executing this function will
stall /not respond to IPIs.
This problem can be... | 0 | static inline int cipso_v4_validate(const struct sk_buff *skb,
unsigned char **option)
{
unsigned char *opt = *option;
unsigned char err_offset = 0;
u8 opt_len = opt[1];
u8 opt_iter;
u8 tag_len;
if (opt_len < 8) {
err_offset = 1;
goto out;
}
if (get_unaligned_be32(&opt[2]) == 0) {
err_offset = 2... | 184,608,763,751,150,730,000,000,000,000,000,000,000 | cipso_ipv4.h | 60,339,981,540,828,350,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-7470 | cipso_v4_validate in include/net/cipso_ipv4.h in the Linux kernel before 3.11.7, when CONFIG_NETLABEL is disabled, allows attackers to cause a denial of service (infinite loop and crash), as demonstrated by icmpsic, a different vulnerability than CVE-2013-0310. | https://nvd.nist.gov/vuln/detail/CVE-2013-7470 |
208,275 | ghostpdl | f54414c8b15b2c27d1dcadd92cfe84f6d15f18dc | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=f54414c8b15b2c27d1dcadd92cfe84f6d15f18dc | Bug 701808: return error from okiibm_print_page1() if x_dpi too high.
Avoids asan error in:
./sanbin/gs -dBATCH -dNOPAUSE -dSAFER -r599 -sOutputFile=tmp -sDEVICE=okiibm ../bug-701808.pdf | 1 | okiibm_print_page1(gx_device_printer *pdev, gp_file *prn_stream, int y_9pin_high,
const char *init_string, int init_length,
const char *end_string, int end_length)
{
static const char graphics_modes_9[5] =
{
-1, 0 /*60*/, 1 /*120*/, -1, 3 /*240*/
};
int in_y_mult = (y_9pin_h... | 237,162,614,944,736,600,000,000,000,000,000,000,000 | gdevokii.c | 158,393,171,947,111,680,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-16301 | A buffer overflow vulnerability in okiibm_print_page1() in devices/gdevokii.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-16301 |
408,168 | ghostpdl | f54414c8b15b2c27d1dcadd92cfe84f6d15f18dc | https://github.com/ArtifexSoftware/ghostpdl | https://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=f54414c8b15b2c27d1dcadd92cfe84f6d15f18dc | Bug 701808: return error from okiibm_print_page1() if x_dpi too high.
Avoids asan error in:
./sanbin/gs -dBATCH -dNOPAUSE -dSAFER -r599 -sOutputFile=tmp -sDEVICE=okiibm ../bug-701808.pdf | 0 | okiibm_print_page1(gx_device_printer *pdev, gp_file *prn_stream, int y_9pin_high,
const char *init_string, int init_length,
const char *end_string, int end_length)
{
static const char graphics_modes_9[5] =
{
-1, 0 /*60*/, 1 /*120*/, -1, 3 /*240*/
};
int in_y_mult;
in... | 133,748,943,666,370,720,000,000,000,000,000,000,000 | gdevokii.c | 168,276,127,667,877,260,000,000,000,000,000,000,000 | [
"CWE-120"
] | CVE-2020-16301 | A buffer overflow vulnerability in okiibm_print_page1() in devices/gdevokii.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-16301 |
208,277 | tor | a74e7fd40f1a77eb4000d8216bb5b80cdd8a6193 | https://github.com/torproject/tor | https://gitweb.torproject.org/tor.git/commitdiff/a74e7fd40f1a77eb4000d8216bb5b80cdd8a6193 | Reject create cells on outgoing OR connections from bridges | 1 | command_process_create_cell(cell_t *cell, or_connection_t *conn)
{
or_circuit_t *circ;
int id_is_high;
if (we_are_hibernating()) {
log_info(LD_OR,
"Received create cell but we're shutting down. Sending back "
"destroy.");
connection_or_send_destroy(cell->circ_id, conn,
... | 195,164,977,295,567,700,000,000,000,000,000,000,000 | command.c | 69,401,693,249,535,750,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2768 | Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selected. | https://nvd.nist.gov/vuln/detail/CVE-2011-2768 |
408,170 | tor | a74e7fd40f1a77eb4000d8216bb5b80cdd8a6193 | https://github.com/torproject/tor | https://gitweb.torproject.org/tor.git/commitdiff/a74e7fd40f1a77eb4000d8216bb5b80cdd8a6193 | Reject create cells on outgoing OR connections from bridges | 0 | command_process_create_cell(cell_t *cell, or_connection_t *conn)
{
or_circuit_t *circ;
or_options_t *options = get_options();
int id_is_high;
if (we_are_hibernating()) {
log_info(LD_OR,
"Received create cell but we're shutting down. Sending back "
"destroy.");
connection_or_se... | 261,180,918,049,439,850,000,000,000,000,000,000,000 | command.c | 211,236,636,070,371,100,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-2768 | Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selected. | https://nvd.nist.gov/vuln/detail/CVE-2011-2768 |
208,337 | libsass | 38f4c3699d06b64128bebc7cf1e8b3125be74dc4 | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/38f4c3699d06b64128bebc7cf1e8b3125be74dc4 | Fix possible bug with handling empty reference combinators
Fixes #2665 | 1 | void Inspect::operator()(Complex_Selector_Ptr c)
{
Compound_Selector_Obj head = c->head();
Complex_Selector_Obj tail = c->tail();
Complex_Selector::Combinator comb = c->combinator();
if (comb == Complex_Selector::ANCESTOR_OF && (!head || head->empty())) {
if (tail) tail->perfo... | 321,471,956,609,770,370,000,000,000,000,000,000,000 | inspect.cpp | 237,047,670,669,665,200,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-11696 | An issue was discovered in LibSass through 3.5.4. A NULL pointer dereference was found in the function Sass::Inspect::operator which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-11696 |
408,633 | libsass | 38f4c3699d06b64128bebc7cf1e8b3125be74dc4 | https://github.com/sass/libsass | https://github.com/sass/libsass/commit/38f4c3699d06b64128bebc7cf1e8b3125be74dc4 | Fix possible bug with handling empty reference combinators
Fixes #2665 | 0 | void Inspect::operator()(Complex_Selector_Ptr c)
{
Compound_Selector_Obj head = c->head();
Complex_Selector_Obj tail = c->tail();
Complex_Selector::Combinator comb = c->combinator();
if (comb == Complex_Selector::ANCESTOR_OF && (!head || head->empty())) {
if (tail) tail->perfo... | 6,099,961,092,201,821,000,000,000,000,000,000,000 | inspect.cpp | 109,207,267,062,082,330,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2018-11696 | An issue was discovered in LibSass through 3.5.4. A NULL pointer dereference was found in the function Sass::Inspect::operator which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact. | https://nvd.nist.gov/vuln/detail/CVE-2018-11696 |
208,359 | mutt | e57a8602b45f58edf7b3ffb61bb17525d75dfcb1 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/commit/e57a8602b45f58edf7b3ffb61bb17525d75dfcb1 | Verify IMAP status mailbox literal count size.
Ensure the length isn't bigger than the idata->buf.
Thanks to Jeriko One fo the bug report and patch, which this commit is
based upon. | 1 | static void cmd_parse_status (IMAP_DATA* idata, char* s)
{
char* mailbox;
char* value;
BUFFY* inc;
IMAP_MBOX mx;
unsigned long ulcount;
unsigned int count;
IMAP_STATUS *status;
unsigned int olduv, oldun;
unsigned int litlen;
short new = 0;
short new_msg_count = 0;
mailbox = imap_next_word (s);
... | 300,452,964,780,632,900,000,000,000,000,000,000,000 | command.c | 274,263,564,788,760,600,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-14351 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size. | https://nvd.nist.gov/vuln/detail/CVE-2018-14351 |
408,766 | mutt | e57a8602b45f58edf7b3ffb61bb17525d75dfcb1 | https://github.com/muttmua/mutt | https://gitlab.com/muttmua/mutt/commit/e57a8602b45f58edf7b3ffb61bb17525d75dfcb1 | Verify IMAP status mailbox literal count size.
Ensure the length isn't bigger than the idata->buf.
Thanks to Jeriko One fo the bug report and patch, which this commit is
based upon. | 0 | static void cmd_parse_status (IMAP_DATA* idata, char* s)
{
char* mailbox;
char* value;
BUFFY* inc;
IMAP_MBOX mx;
unsigned long ulcount;
unsigned int count;
IMAP_STATUS *status;
unsigned int olduv, oldun;
unsigned int litlen;
short new = 0;
short new_msg_count = 0;
mailbox = imap_next_word (s);
... | 259,706,192,215,179,850,000,000,000,000,000,000,000 | command.c | 169,809,151,969,429,160,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2018-14351 | An issue was discovered in Mutt before 1.10.1 and NeoMutt before 2018-07-16. imap/command.c mishandles a long IMAP status mailbox literal count size. | https://nvd.nist.gov/vuln/detail/CVE-2018-14351 |
208,361 | curl | 6efd2fa529a189bf41736a610f6184cd8ad94b4d | https://github.com/curl/curl | https://github.com/curl/curl/commit/6efd2fa529a189bf41736a610f6184cd8ad94b4d | mbedtls/polarssl: set "hostname" unconditionally
...as otherwise the TLS libs will skip the CN/SAN check and just allow
connection to any server. curl previously skipped this function when SNI
wasn't used or when connecting to an IP address specified host.
CVE-2016-3739
Bug: https://curl.haxx.se/docs/adv_20160518A.h... | 1 | mbed_connect_step1(struct connectdata *conn,
int sockindex)
{
struct SessionHandle *data = conn->data;
struct ssl_connect_data* connssl = &conn->ssl[sockindex];
bool sni = TRUE; /* default is SNI enabled */
int ret = -1;
#ifdef ENABLE_IPV6
struct in6_addr addr;
#else
struct in_addr addr;... | 133,043,167,836,266,980,000,000,000,000,000,000,000 | mbedtls.c | 73,562,380,360,790,785,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-3739 | The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and libcurl before 7.49.0, when using SSLv3 or making a TLS connection to a URL that uses a numerical IP address, allow remote attackers to spoof servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2016-3739 |
408,822 | curl | 6efd2fa529a189bf41736a610f6184cd8ad94b4d | https://github.com/curl/curl | https://github.com/curl/curl/commit/6efd2fa529a189bf41736a610f6184cd8ad94b4d | mbedtls/polarssl: set "hostname" unconditionally
...as otherwise the TLS libs will skip the CN/SAN check and just allow
connection to any server. curl previously skipped this function when SNI
wasn't used or when connecting to an IP address specified host.
CVE-2016-3739
Bug: https://curl.haxx.se/docs/adv_20160518A.h... | 0 | mbed_connect_step1(struct connectdata *conn,
int sockindex)
{
struct SessionHandle *data = conn->data;
struct ssl_connect_data* connssl = &conn->ssl[sockindex];
bool sni = TRUE; /* default is SNI enabled */
int ret = -1;
#ifdef ENABLE_IPV6
struct in6_addr addr;
#else
struct in_addr addr;... | 58,691,140,819,368,790,000,000,000,000,000,000,000 | mbedtls.c | 127,704,493,926,411,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-3739 | The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and libcurl before 7.49.0, when using SSLv3 or making a TLS connection to a URL that uses a numerical IP address, allow remote attackers to spoof servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2016-3739 |
208,362 | curl | 6efd2fa529a189bf41736a610f6184cd8ad94b4d | https://github.com/curl/curl | https://github.com/curl/curl/commit/6efd2fa529a189bf41736a610f6184cd8ad94b4d | mbedtls/polarssl: set "hostname" unconditionally
...as otherwise the TLS libs will skip the CN/SAN check and just allow
connection to any server. curl previously skipped this function when SNI
wasn't used or when connecting to an IP address specified host.
CVE-2016-3739
Bug: https://curl.haxx.se/docs/adv_20160518A.h... | 1 | polarssl_connect_step1(struct connectdata *conn,
int sockindex)
{
struct SessionHandle *data = conn->data;
struct ssl_connect_data* connssl = &conn->ssl[sockindex];
bool sni = TRUE; /* default is SNI enabled */
int ret = -1;
#ifdef ENABLE_IPV6
struct in6_addr addr;
#else
struct in_addr... | 126,006,149,552,308,340,000,000,000,000,000,000,000 | polarssl.c | 242,970,519,968,481,220,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-3739 | The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and libcurl before 7.49.0, when using SSLv3 or making a TLS connection to a URL that uses a numerical IP address, allow remote attackers to spoof servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2016-3739 |
408,829 | curl | 6efd2fa529a189bf41736a610f6184cd8ad94b4d | https://github.com/curl/curl | https://github.com/curl/curl/commit/6efd2fa529a189bf41736a610f6184cd8ad94b4d | mbedtls/polarssl: set "hostname" unconditionally
...as otherwise the TLS libs will skip the CN/SAN check and just allow
connection to any server. curl previously skipped this function when SNI
wasn't used or when connecting to an IP address specified host.
CVE-2016-3739
Bug: https://curl.haxx.se/docs/adv_20160518A.h... | 0 | polarssl_connect_step1(struct connectdata *conn,
int sockindex)
{
struct SessionHandle *data = conn->data;
struct ssl_connect_data* connssl = &conn->ssl[sockindex];
bool sni = TRUE; /* default is SNI enabled */
int ret = -1;
#ifdef ENABLE_IPV6
struct in6_addr addr;
#else
struct in_addr... | 23,175,505,753,922,500,000,000,000,000,000,000,000 | polarssl.c | 74,419,136,145,754,480,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2016-3739 | The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and libcurl before 7.49.0, when using SSLv3 or making a TLS connection to a URL that uses a numerical IP address, allow remote attackers to spoof servers via an arbitrary valid certificate. | https://nvd.nist.gov/vuln/detail/CVE-2016-3739 |
208,371 | samba | 8d34d172092f71baad0d777567e49aebfa07313d | https://github.com/samba-team/samba | https://git.samba.org/?p=samba.git;a=commit;h=8d34d172092f71baad0d777567e49aebfa07313d | CVE-2019-3824 ldb: ldb_parse_tree use talloc_zero
Initialise the created ldb_parse_tree with talloc_zero, this ensures
that it is correctly initialised if inadvertently passed to a function
expecting a different operation type.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13773
Signed-off-by: Gary Lockyer <gary@c... | 1 | static struct ldb_parse_tree *ldb_parse_simple(TALLOC_CTX *mem_ctx, const char **s)
{
char *attr, *value;
struct ldb_parse_tree *ret;
enum ldb_parse_op filtertype;
ret = talloc(mem_ctx, struct ldb_parse_tree);
if (!ret) {
errno = ENOMEM;
return NULL;
}
filtertype = ldb_parse_filtertype(ret, &attr, &value, ... | 163,133,602,224,524,550,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-3824 | A flaw was found in the way an LDAP search expression could crash the shared LDAP server process of a samba AD DC in samba before version 4.10. An authenticated user, having read permissions on the LDAP server, could use this flaw to cause denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2019-3824 |
408,985 | samba | 8d34d172092f71baad0d777567e49aebfa07313d | https://github.com/samba-team/samba | https://git.samba.org/?p=samba.git;a=commit;h=8d34d172092f71baad0d777567e49aebfa07313d | CVE-2019-3824 ldb: ldb_parse_tree use talloc_zero
Initialise the created ldb_parse_tree with talloc_zero, this ensures
that it is correctly initialised if inadvertently passed to a function
expecting a different operation type.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13773
Signed-off-by: Gary Lockyer <gary@c... | 0 | static struct ldb_parse_tree *ldb_parse_simple(TALLOC_CTX *mem_ctx, const char **s)
{
char *attr, *value;
struct ldb_parse_tree *ret;
enum ldb_parse_op filtertype;
ret = talloc_zero(mem_ctx, struct ldb_parse_tree);
if (!ret) {
errno = ENOMEM;
return NULL;
}
filtertype = ldb_parse_filtertype(ret, &attr, &va... | 197,391,844,608,473,230,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2019-3824 | A flaw was found in the way an LDAP search expression could crash the shared LDAP server process of a samba AD DC in samba before version 4.10. An authenticated user, having read permissions on the LDAP server, could use this flaw to cause denial of service. | https://nvd.nist.gov/vuln/detail/CVE-2019-3824 |
208,376 | LibRaw | 20ad21c0d87ca80217aee47533d91e633ce1864d | https://github.com/LibRaw/LibRaw | https://github.com/LibRaw/LibRaw/commit/20ad21c0d87ca80217aee47533d91e633ce1864d | Thumbnail size range check | 1 | 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;
// some kodak ca... | 208,836,291,184,873,500,000,000,000,000,000,000,000 | thumb_utils.cpp | 54,602,646,590,527,250,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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.