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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
503,367 | openssl | 380f18ed5f140e0ae1b68f3ab8f4f7c395658d9e | https://github.com/openssl/openssl | http://git.openssl.org/?p=openssl.git;a=commitdiff;h=380f18ed5f140e0ae1b68f3ab8f4f7c395658d9e | CVE-2016-0798: avoid memory leak in SRP
The SRP user database lookup method SRP_VBASE_get_by_user had confusing
memory management semantics; the returned pointer was sometimes newly
allocated, and sometimes owned by the callee. The calling code has no
way of distinguishing these two cases.
Specifically, SRP servers t... | 0 | SRP_user_pwd *SRP_VBASE_get1_by_user(SRP_VBASE *vb, char *username)
{
SRP_user_pwd *user;
unsigned char digv[SHA_DIGEST_LENGTH];
unsigned char digs[SHA_DIGEST_LENGTH];
EVP_MD_CTX *ctxt = NULL;
if (vb == NULL)
return NULL;
if ((user = find_user(vb, username)) != NULL)
return srp... | 241,597,973,478,698,200,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2016-0798 | Memory leak in the SRP_VBASE_get_by_user implementation in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory consumption) by providing an invalid username in a connection attempt, related to apps/s_server.c and crypto/srp/srp_vfy.c. | https://nvd.nist.gov/vuln/detail/CVE-2016-0798 |
216,584 | openssl | 9cb177301fdab492e4cfef376b28339afe3ef663 | https://github.com/openssl/openssl | http://git.openssl.org/?p=openssl.git;a=commitdiff;h=9cb177301fdab492e4cfef376b28339afe3ef663 | Fix memory issues in BIO_*printf functions
The internal |fmtstr| function used in processing a "%s" format string
in the BIO_*printf functions could overflow while calculating the length
of a string and cause an OOB read when printing very long strings.
Additionally the internal |doapr_outch| function can attempt to ... | 1 | fmtstr(char **sbuffer,
char **buffer,
size_t *currlen,
size_t *maxlen, const char *value, int flags, int min, int max)
{
int padlen, strln;
int cnt = 0;
if (value == 0)
value = "<NULL>";
for (strln = 0; value[strln]; ++strln) ;
padlen = min - strln;
if (padlen < 0)
... | 299,005,559,393,919,730,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-0799 | The fmtstr function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g improperly calculates string lengths, which allows remote attackers to cause a denial of service (overflow and out-of-bounds read) or possibly have unspecified other impact via a long string, as demonstrated by a large am... | https://nvd.nist.gov/vuln/detail/CVE-2016-0799 |
503,421 | openssl | 9cb177301fdab492e4cfef376b28339afe3ef663 | https://github.com/openssl/openssl | http://git.openssl.org/?p=openssl.git;a=commitdiff;h=9cb177301fdab492e4cfef376b28339afe3ef663 | Fix memory issues in BIO_*printf functions
The internal |fmtstr| function used in processing a "%s" format string
in the BIO_*printf functions could overflow while calculating the length
of a string and cause an OOB read when printing very long strings.
Additionally the internal |doapr_outch| function can attempt to ... | 0 | fmtstr(char **sbuffer,
char **buffer,
size_t *currlen,
size_t *maxlen, const char *value, int flags, int min, int max)
{
int padlen;
size_t strln;
int cnt = 0;
if (value == 0)
value = "<NULL>";
strln = strlen(value);
if (strln > INT_MAX)
strln = INT_MAX;
... | 124,968,009,864,863,420,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-0799 | The fmtstr function in crypto/bio/b_print.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g improperly calculates string lengths, which allows remote attackers to cause a denial of service (overflow and out-of-bounds read) or possibly have unspecified other impact via a long string, as demonstrated by a large am... | https://nvd.nist.gov/vuln/detail/CVE-2016-0799 |
216,591 | openssl | 4159f311671cf3bac03815e5de44681eb758304a | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=4159f311671cf3bac03815e5de44681eb758304a | Check that we have enough padding characters.
Reviewed-by: Emilia Käsper <emilia@openssl.org>
CVE-2016-2107
MR: #2572 | 1 | static int aesni_cbc_hmac_sha1_cipher(EVP_CIPHER_CTX *ctx, unsigned char *out,
const unsigned char *in, size_t len)
{
EVP_AES_HMAC_SHA1 *key = data(ctx);
unsigned int l;
size_t plen = key->payload_length, iv = 0, /* explicit IV in TLS 1.1 and
... | 192,832,648,775,476,000,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2016-2107 | The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an inc... | https://nvd.nist.gov/vuln/detail/CVE-2016-2107 |
503,433 | openssl | 4159f311671cf3bac03815e5de44681eb758304a | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=4159f311671cf3bac03815e5de44681eb758304a | Check that we have enough padding characters.
Reviewed-by: Emilia Käsper <emilia@openssl.org>
CVE-2016-2107
MR: #2572 | 0 | static int aesni_cbc_hmac_sha1_cipher(EVP_CIPHER_CTX *ctx, unsigned char *out,
const unsigned char *in, size_t len)
{
EVP_AES_HMAC_SHA1 *key = data(ctx);
unsigned int l;
size_t plen = key->payload_length, iv = 0, /* explicit IV in TLS 1.1 and
... | 21,898,493,393,794,565,000,000,000,000,000,000,000 | None | null | [
"CWE-310"
] | CVE-2016-2107 | The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an inc... | https://nvd.nist.gov/vuln/detail/CVE-2016-2107 |
216,604 | node | fcb9145e291e8cb82164bc1fe3db1c1dae219b55 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/fcb9145e291e8cb82164bc1fe3db1c1dae219b55 | deps: backport 3a9bfec from v8 upstream
Some of the logic from `zone.cc` is found in `zone-inl.h` in this
release stream.
Original commit message:
Fix overflow issue in Zone::New
When requesting a large allocation near the end of the address space,
the computation could overflow and erroneously *not* grow the... | 1 | inline void* Zone::New(int size) {
ASSERT(scope_nesting_ > 0);
// Round up the requested size to fit the alignment.
size = RoundUp(size, kAlignment);
// If the allocation size is divisible by 8 then we return an 8-byte aligned
// address.
if (kPointerSize == 4 && kAlignment == 4) {
position_ += ((~size... | 177,682,813,053,259,400,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-1669 | The Zone::New function in zone.cc in Google V8 before 5.0.71.47, as used in Google Chrome before 50.0.2661.102, does not properly determine when to expand certain memory allocations, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via crafted JavaSc... | https://nvd.nist.gov/vuln/detail/CVE-2016-1669 |
503,612 | node | fcb9145e291e8cb82164bc1fe3db1c1dae219b55 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/fcb9145e291e8cb82164bc1fe3db1c1dae219b55 | deps: backport 3a9bfec from v8 upstream
Some of the logic from `zone.cc` is found in `zone-inl.h` in this
release stream.
Original commit message:
Fix overflow issue in Zone::New
When requesting a large allocation near the end of the address space,
the computation could overflow and erroneously *not* grow the... | 0 | inline void* Zone::New(int size) {
ASSERT(scope_nesting_ > 0);
// Round up the requested size to fit the alignment.
size = RoundUp(size, kAlignment);
// If the allocation size is divisible by 8 then we return an 8-byte aligned
// address.
if (kPointerSize == 4 && kAlignment == 4) {
position_ += ((~size... | 55,488,666,735,448,390,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-1669 | The Zone::New function in zone.cc in Google V8 before 5.0.71.47, as used in Google Chrome before 50.0.2661.102, does not properly determine when to expand certain memory allocations, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via crafted JavaSc... | https://nvd.nist.gov/vuln/detail/CVE-2016-1669 |
216,615 | openssl | 07bed46f332fce8c1d157689a2cdf915a982ae34 | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commit;h=07bed46f332fce8c1d157689a2cdf915a982ae34 | Check for errors in BN_bn2dec()
If an oversize BIGNUM is presented to BN_bn2dec() it can cause
BN_div_word() to fail and not reduce the value of 't' resulting
in OOB writes to the bn_data buffer and eventually crashing.
Fix by checking return value of BN_div_word() and checking writes
don't overflow buffer.
Thanks t... | 1 | char *BN_bn2dec(const BIGNUM *a)
{
int i = 0, num, ok = 0;
char *buf = NULL;
char *p;
BIGNUM *t = NULL;
BN_ULONG *bn_data = NULL, *lp;
/*-
* get an upper bound for the length of the decimal integer
* num <= (BN_num_bits(a) + 1) * log(2)
* <= 3 * BN_num_bits(a) * 0.1001 + log(... | 73,163,607,733,817,450,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-2182 | The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-2182 |
503,663 | openssl | 07bed46f332fce8c1d157689a2cdf915a982ae34 | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commit;h=07bed46f332fce8c1d157689a2cdf915a982ae34 | Check for errors in BN_bn2dec()
If an oversize BIGNUM is presented to BN_bn2dec() it can cause
BN_div_word() to fail and not reduce the value of 't' resulting
in OOB writes to the bn_data buffer and eventually crashing.
Fix by checking return value of BN_div_word() and checking writes
don't overflow buffer.
Thanks t... | 0 | char *BN_bn2dec(const BIGNUM *a)
{
int i = 0, num, ok = 0;
char *buf = NULL;
char *p;
BIGNUM *t = NULL;
BN_ULONG *bn_data = NULL, *lp;
int bn_data_num;
/*-
* get an upper bound for the length of the decimal integer
* num <= (BN_num_bits(a) + 1) * log(2)
* <= 3 * BN_num_bi... | 168,818,854,548,294,070,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-2182 | The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-2182 |
216,616 | openssl | 3612ff6fcec0e3d1f2a598135fe12177c0419582 | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=3612ff6fcec0e3d1f2a598135fe12177c0419582 | Fix overflow check in BN_bn2dec()
Fix an off by one error in the overflow check added by 07bed46f332fc
("Check for errors in BN_bn2dec()").
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(cherry picked from commit 099e2968ed3c7d256cda048995626664082b1b30) | 1 | char *BN_bn2dec(const BIGNUM *a)
{
int i = 0, num, ok = 0;
char *buf = NULL;
char *p;
BIGNUM *t = NULL;
BN_ULONG *bn_data = NULL, *lp;
int bn_data_num;
/*-
* get an upper bound for the length of the decimal integer
* num <= (BN_num_bits(a) + 1) * log(2)
* <= 3 * BN_num_bi... | 58,310,321,551,122,590,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-2182 | The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-2182 |
503,666 | openssl | 3612ff6fcec0e3d1f2a598135fe12177c0419582 | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=3612ff6fcec0e3d1f2a598135fe12177c0419582 | Fix overflow check in BN_bn2dec()
Fix an off by one error in the overflow check added by 07bed46f332fc
("Check for errors in BN_bn2dec()").
Reviewed-by: Stephen Henson <steve@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(cherry picked from commit 099e2968ed3c7d256cda048995626664082b1b30) | 0 | char *BN_bn2dec(const BIGNUM *a)
{
int i = 0, num, ok = 0;
char *buf = NULL;
char *p;
BIGNUM *t = NULL;
BN_ULONG *bn_data = NULL, *lp;
int bn_data_num;
/*-
* get an upper bound for the length of the decimal integer
* num <= (BN_num_bits(a) + 1) * log(2)
* <= 3 * BN_num_bi... | 269,679,746,576,233,400,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2016-2182 | The BN_bn2dec function in crypto/bn/bn_print.c in OpenSSL before 1.1.0 does not properly validate division results, which allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly have unspecified other impact via unknown vectors. | https://nvd.nist.gov/vuln/detail/CVE-2016-2182 |
216,629 | openssl | cfd40fd39e69f5e3c654ae8fbf9acb1d2a051144 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/cfd40fd39e69f5e3c654ae8fbf9acb1d2a051144 | Prevent DTLS Finished message injection
Follow on from CVE-2016-2179
The investigation and analysis of CVE-2016-2179 highlighted a related flaw.
This commit fixes a security "near miss" in the buffered message handling
code. Ultimately this is not currently believed to be exploitable due to
the reasons outlined belo... | 1 | void dtls1_reset_seq_numbers(SSL *s, int rw)
{
unsigned char *seq;
unsigned int seq_bytes = sizeof(s->s3->read_sequence);
if (rw & SSL3_CC_READ) {
seq = s->s3->read_sequence;
s->d1->r_epoch++;
memcpy(&(s->d1->bitmap), &(s->d1->next_bitmap), sizeof(DTLS1_BITMAP));
memset(&(s-... | 273,181,594,329,290,830,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2016-2179 | The DTLS implementation in OpenSSL before 1.1.0 does not properly restrict the lifetime of queue entries associated with unused out-of-order messages, which allows remote attackers to cause a denial of service (memory consumption) by maintaining many crafted DTLS sessions simultaneously, related to d1_lib.c, statem_dtl... | https://nvd.nist.gov/vuln/detail/CVE-2016-2179 |
503,738 | openssl | cfd40fd39e69f5e3c654ae8fbf9acb1d2a051144 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/cfd40fd39e69f5e3c654ae8fbf9acb1d2a051144 | Prevent DTLS Finished message injection
Follow on from CVE-2016-2179
The investigation and analysis of CVE-2016-2179 highlighted a related flaw.
This commit fixes a security "near miss" in the buffered message handling
code. Ultimately this is not currently believed to be exploitable due to
the reasons outlined belo... | 0 | void dtls1_reset_seq_numbers(SSL *s, int rw)
{
unsigned char *seq;
unsigned int seq_bytes = sizeof(s->s3->read_sequence);
if (rw & SSL3_CC_READ) {
seq = s->s3->read_sequence;
s->d1->r_epoch++;
memcpy(&(s->d1->bitmap), &(s->d1->next_bitmap), sizeof(DTLS1_BITMAP));
memset(&(s-... | 68,381,293,336,199,120,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2016-2179 | The DTLS implementation in OpenSSL before 1.1.0 does not properly restrict the lifetime of queue entries associated with unused out-of-order messages, which allows remote attackers to cause a denial of service (memory consumption) by maintaining many crafted DTLS sessions simultaneously, related to d1_lib.c, statem_dtl... | https://nvd.nist.gov/vuln/detail/CVE-2016-2179 |
216,630 | openssl | 1bbe48ab149893a78bf99c8eb8895c928900a16f | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/1bbe48ab149893a78bf99c8eb8895c928900a16f | Sanity check ticket length.
If a ticket callback changes the HMAC digest to SHA512 the existing
sanity checks are not sufficient and an attacker could perform a DoS
attack with a malformed ticket. Add additional checks based on
HMAC size.
Thanks to Shi Lei for reporting this bug.
CVE-2016-6302
Reviewed-by: Rich Sal... | 1 | static int tls_decrypt_ticket(SSL *s, const unsigned char *etick,
int eticklen, const unsigned char *sess_id,
int sesslen, SSL_SESSION **psess)
{
SSL_SESSION *sess;
unsigned char *sdec;
const unsigned char *p;
int slen, mlen, renew_ticket = 0;
... | 281,901,224,920,790,530,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-6302 | The tls_decrypt_ticket function in ssl/t1_lib.c in OpenSSL before 1.1.0 does not consider the HMAC size during validation of the ticket length, which allows remote attackers to cause a denial of service via a ticket that is too short. | https://nvd.nist.gov/vuln/detail/CVE-2016-6302 |
16,373 | openssl | 2c0d295e26306e15a92eb23a84a1802005c1c137 | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=2c0d295e26306e15a92eb23a84a1802005c1c137 | Fix OCSP Status Request extension unbounded memory growth
A malicious client can send an excessively large OCSP Status Request
extension. If that client continually requests renegotiation,
sending a large OCSP Status Request extension each time, then there will
be unbounded memory growth on the server. This will event... | 0 | static int tls_decrypt_ticket(SSL *s, const unsigned char *etick,
int eticklen, const unsigned char *sess_id,
int sesslen, SSL_SESSION **psess)
{
SSL_SESSION *sess;
unsigned char *sdec;
const unsigned char *p;
int slen, mlen, renew_ticket = 0;
... | 50,794,026,404,427,530,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2016-6304 | Multiple memory leaks in t1_lib.c in OpenSSL before 1.0.1u, 1.0.2 before 1.0.2i, and 1.1.0 before 1.1.0a allow remote attackers to cause a denial of service (memory consumption) via large OCSP Status Request extensions. | https://nvd.nist.gov/vuln/detail/CVE-2016-6304 |
216,638 | libtiff | b5d6803f0898e931cf772d3d0755704ab8488e63 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/b5d6803f0898e931cf772d3d0755704ab8488e63 | * tools/tiff2pdf.c: fix write buffer overflow of 2 bytes on JPEG
compressed images. Reported by Tyler Bohan of Cisco Talos as
TALOS-CAN-0187 / CVE-2016-5652.
Also prevents writing 2 extra uninitialized bytes to the file stream. | 1 | tsize_t t2p_readwrite_pdf_image_tile(T2P* t2p, TIFF* input, TIFF* output, ttile_t tile){
uint16 edge=0;
tsize_t written=0;
unsigned char* buffer=NULL;
tsize_t bufferoffset=0;
unsigned char* samplebuffer=NULL;
tsize_t samplebufferoffset=0;
tsize_t read=0;
uint16 i=0;
ttile_t tilecount=0;
/* tsize_t tilesize=0... | 81,262,399,064,058,510,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-5652 | An exploitable heap-based buffer overflow exists in the handling of TIFF images in LibTIFF's TIFF2PDF tool. A crafted TIFF document can lead to a heap-based buffer overflow resulting in remote code execution. Vulnerability can be triggered via a saved TIFF file delivered by other means. | https://nvd.nist.gov/vuln/detail/CVE-2016-5652 |
503,903 | libtiff | b5d6803f0898e931cf772d3d0755704ab8488e63 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/b5d6803f0898e931cf772d3d0755704ab8488e63 | * tools/tiff2pdf.c: fix write buffer overflow of 2 bytes on JPEG
compressed images. Reported by Tyler Bohan of Cisco Talos as
TALOS-CAN-0187 / CVE-2016-5652.
Also prevents writing 2 extra uninitialized bytes to the file stream. | 0 | tsize_t t2p_readwrite_pdf_image_tile(T2P* t2p, TIFF* input, TIFF* output, ttile_t tile){
uint16 edge=0;
tsize_t written=0;
unsigned char* buffer=NULL;
tsize_t bufferoffset=0;
unsigned char* samplebuffer=NULL;
tsize_t samplebufferoffset=0;
tsize_t read=0;
uint16 i=0;
ttile_t tilecount=0;
/* tsize_t tilesize=0... | 190,316,883,070,534,820,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2016-5652 | An exploitable heap-based buffer overflow exists in the handling of TIFF images in LibTIFF's TIFF2PDF tool. A crafted TIFF document can lead to a heap-based buffer overflow resulting in remote code execution. Vulnerability can be triggered via a saved TIFF file delivered by other means. | https://nvd.nist.gov/vuln/detail/CVE-2016-5652 |
216,653 | core | 1f2c35da2b96905bec6e45f88af0f33ee63789e6 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/1f2c35da2b96905bec6e45f88af0f33ee63789e6 | auth: Fix auth-policy crash when username is NULL
If SASL request is invalid, or incomplete, and username
is left NULL, handle it gracefully by adding just
NUL byte in auth policy digest for username. | 1 | void auth_policy_create_json(struct policy_lookup_ctx *context,
const char *password, bool include_success)
{
const struct var_expand_table *var_table;
context->json = str_new(context->pool, 64);
unsigned char *ptr;
const struct hash_method *digest = hash_method_lookup(context->set->policy_hash_mech);
i_assert(d... | 174,969,646,508,072,500,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-8652 | The auth component in Dovecot before 2.2.27, when auth-policy is configured, allows a remote attackers to cause a denial of service (crash) by aborting authentication without setting a username. | https://nvd.nist.gov/vuln/detail/CVE-2016-8652 |
503,965 | core | 1f2c35da2b96905bec6e45f88af0f33ee63789e6 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/1f2c35da2b96905bec6e45f88af0f33ee63789e6 | auth: Fix auth-policy crash when username is NULL
If SASL request is invalid, or incomplete, and username
is left NULL, handle it gracefully by adding just
NUL byte in auth policy digest for username. | 0 | void auth_policy_create_json(struct policy_lookup_ctx *context,
const char *password, bool include_success)
{
const struct var_expand_table *var_table;
context->json = str_new(context->pool, 64);
unsigned char *ptr;
const struct hash_method *digest = hash_method_lookup(context->set->policy_hash_mech);
i_assert(d... | 86,117,927,478,741,330,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2016-8652 | The auth component in Dovecot before 2.2.27, when auth-policy is configured, allows a remote attackers to cause a denial of service (crash) by aborting authentication without setting a username. | https://nvd.nist.gov/vuln/detail/CVE-2016-8652 |
216,659 | openssl | 8e20499629b6bcf868d0072c7011e590b5c2294d | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=8e20499629b6bcf868d0072c7011e590b5c2294d | crypto/evp: harden RC4_MD5 cipher.
Originally a crash in 32-bit build was reported CHACHA20-POLY1305
cipher. The crash is triggered by truncated packet and is result
of excessive hashing to the edge of accessible memory (or bogus
MAC value is produced if x86 MD5 assembly module is involved). Since
hash operation is re... | 1 | static int rc4_hmac_md5_ctrl(EVP_CIPHER_CTX *ctx, int type, int arg,
void *ptr)
{
EVP_RC4_HMAC_MD5 *key = data(ctx);
switch (type) {
case EVP_CTRL_AEAD_SET_MAC_KEY:
{
unsigned int i;
unsigned char hmac_key[64];
memset(hmac_key, 0, si... | 326,665,067,488,901,900,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-3731 | If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1... | https://nvd.nist.gov/vuln/detail/CVE-2017-3731 |
504,045 | openssl | 8e20499629b6bcf868d0072c7011e590b5c2294d | https://github.com/openssl/openssl | https://git.openssl.org/?p=openssl.git;a=commitdiff;h=8e20499629b6bcf868d0072c7011e590b5c2294d | crypto/evp: harden RC4_MD5 cipher.
Originally a crash in 32-bit build was reported CHACHA20-POLY1305
cipher. The crash is triggered by truncated packet and is result
of excessive hashing to the edge of accessible memory (or bogus
MAC value is produced if x86 MD5 assembly module is involved). Since
hash operation is re... | 0 | static int rc4_hmac_md5_ctrl(EVP_CIPHER_CTX *ctx, int type, int arg,
void *ptr)
{
EVP_RC4_HMAC_MD5 *key = data(ctx);
switch (type) {
case EVP_CTRL_AEAD_SET_MAC_KEY:
{
unsigned int i;
unsigned char hmac_key[64];
memset(hmac_key, 0, si... | 79,092,581,611,569,120,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2017-3731 | If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1... | https://nvd.nist.gov/vuln/detail/CVE-2017-3731 |
216,666 | server | eef21014898d61e77890359d6546d4985d829ef6 | https://github.com/MariaDB/server | https://github.com/MariaDB/server/commit/eef21014898d61e77890359d6546d4985d829ef6 | MDEV-11933 Wrong usage of linked list in mysql_prune_stmt_list
mysql_prune_stmt_list() was walking the list following
element->next pointers, but inside the loop it was invoking
list_add(element) that modified element->next. So, mysql_prune_stmt_list()
failed to visit and reset all elements, and some of them were left... | 1 | static void mysql_prune_stmt_list(MYSQL *mysql)
{
LIST *element= mysql->stmts;
LIST *pruned_list= 0;
for (; element; element= element->next)
{
MYSQL_STMT *stmt= (MYSQL_STMT *) element->data;
if (stmt->state != MYSQL_STMT_INIT_DONE)
{
stmt->mysql= 0;
stmt->last_errno= CR_SERVER_LOST;
... | 317,665,458,119,443,430,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-3302 | Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29, 10.1.x through 10.1.21, and 10.2.x through 10.2.3. | https://nvd.nist.gov/vuln/detail/CVE-2017-3302 |
504,113 | server | eef21014898d61e77890359d6546d4985d829ef6 | https://github.com/MariaDB/server | https://github.com/MariaDB/server/commit/eef21014898d61e77890359d6546d4985d829ef6 | MDEV-11933 Wrong usage of linked list in mysql_prune_stmt_list
mysql_prune_stmt_list() was walking the list following
element->next pointers, but inside the loop it was invoking
list_add(element) that modified element->next. So, mysql_prune_stmt_list()
failed to visit and reset all elements, and some of them were left... | 0 | static void mysql_prune_stmt_list(MYSQL *mysql)
{
LIST *element= mysql->stmts;
for (; element; element= element->next)
{
MYSQL_STMT *stmt= (MYSQL_STMT *) element->data;
if (stmt->state != MYSQL_STMT_INIT_DONE)
{
stmt->mysql= 0;
stmt->last_errno= CR_SERVER_LOST;
strmov(stmt->last_erro... | 162,945,344,355,472,890,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2017-3302 | Crash in libmysqlclient.so in Oracle MySQL before 5.6.21 and 5.7.x before 5.7.5 and MariaDB through 5.5.54, 10.0.x through 10.0.29, 10.1.x through 10.1.21, and 10.2.x through 10.2.3. | https://nvd.nist.gov/vuln/detail/CVE-2017-3302 |
216,682 | core | 000030feb7a30f193197f1aab8a7b04a26b42735 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/000030feb7a30f193197f1aab8a7b04a26b42735.patch | auth: Do not double-expand key in passdb dict when authenticating
Broken by 79042f8c | 1 | static int db_dict_iter_lookup_key_values(struct db_dict_value_iter *iter)
{
struct db_dict_iter_key *key;
string_t *path;
const char *error;
int ret;
/* sort the keys so that we'll first lookup the keys without
default value. if their lookup fails, the user doesn't exist. */
array_sort(&iter->keys, db_dict_... | 65,901,651,756,191,940,000,000,000,000,000,000,000 | None | null | [
"CWE-284"
] | CVE-2017-2669 | Dovecot before version 2.2.29 is vulnerable to a denial of service. When 'dict' passdb and userdb were used for user authentication, the username sent by the IMAP/POP3 client was sent through var_expand() to perform %variable expansion. Sending specially crafted %variable fields could result in excessive memory usage c... | https://nvd.nist.gov/vuln/detail/CVE-2017-2669 |
504,406 | core | 000030feb7a30f193197f1aab8a7b04a26b42735 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/000030feb7a30f193197f1aab8a7b04a26b42735.patch | auth: Do not double-expand key in passdb dict when authenticating
Broken by 79042f8c | 0 | static int db_dict_iter_lookup_key_values(struct db_dict_value_iter *iter)
{
struct db_dict_iter_key *key;
string_t *path;
const char *error;
int ret;
/* sort the keys so that we'll first lookup the keys without
default value. if their lookup fails, the user doesn't exist. */
array_sort(&iter->keys, db_dict_... | 237,433,190,094,419,900,000,000,000,000,000,000,000 | None | null | [
"CWE-284"
] | CVE-2017-2669 | Dovecot before version 2.2.29 is vulnerable to a denial of service. When 'dict' passdb and userdb were used for user authentication, the username sent by the IMAP/POP3 client was sent through var_expand() to perform %variable expansion. Sending specially crafted %variable fields could result in excessive memory usage c... | https://nvd.nist.gov/vuln/detail/CVE-2017-2669 |
216,683 | libtiff | 48780b4fcc425cddc4ef8ffdf536f96a0d1b313b | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/48780b4fcc425cddc4ef8ffdf536f96a0d1b313b | * libtiff/tif_getimage.c: add explicit uint32 cast in putagreytile to
avoid UndefinedBehaviorSanitizer warning.
Patch by Nicolás Peña.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2658 | 1 | DECLAREContigPutFunc(putagreytile)
{
int samplesperpixel = img->samplesperpixel;
uint32** BWmap = img->BWmap;
(void) y;
while (h-- > 0) {
for (x = w; x-- > 0;)
{
*cp++ = BWmap[*pp][0] & (*(pp+1) << 24 | ~A1);
pp += samplesperpixel;
}
cp += toskew;
pp += fromsk... | 125,156,244,755,475,250,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-7592 | The putagreytile function in tif_getimage.c in LibTIFF 4.0.7 has a left-shift undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2017-7592 |
504,410 | libtiff | 48780b4fcc425cddc4ef8ffdf536f96a0d1b313b | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/48780b4fcc425cddc4ef8ffdf536f96a0d1b313b | * libtiff/tif_getimage.c: add explicit uint32 cast in putagreytile to
avoid UndefinedBehaviorSanitizer warning.
Patch by Nicolás Peña.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2658 | 0 | DECLAREContigPutFunc(putagreytile)
{
int samplesperpixel = img->samplesperpixel;
uint32** BWmap = img->BWmap;
(void) y;
while (h-- > 0) {
for (x = w; x-- > 0;)
{
*cp++ = BWmap[*pp][0] & ((uint32)*(pp+1) << 24 | ~A1);
pp += samplesperpixel;
}
cp += toskew;
pp +... | 165,423,150,374,571,270,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-7592 | The putagreytile function in tif_getimage.c in LibTIFF 4.0.7 has a left-shift undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2017-7592 |
216,696 | libtiff | 0a76a8c765c7b8327c59646284fa78c3c27e5490 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/0a76a8c765c7b8327c59646284fa78c3c27e5490 | * libtiff/tif_jpeg.c: validate BitsPerSample in JPEGSetupEncode() to avoid
undefined behaviour caused by invalid shift exponent.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2648 | 1 | JPEGSetupEncode(TIFF* tif)
{
JPEGState* sp = JState(tif);
TIFFDirectory *td = &tif->tif_dir;
static const char module[] = "JPEGSetupEncode";
#if defined(JPEG_DUAL_MODE_8_12) && !defined(TIFFInitJPEG)
if( tif->tif_dir.td_bitspersample == 12 )
return TIFFReInitJPEG_12( tif, COMPRESSION_JPEG, 1 );
... | 269,457,404,244,354,800,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-7601 | LibTIFF 4.0.7 has a "shift exponent too large for 64-bit type long" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2017-7601 |
504,508 | libtiff | 0a76a8c765c7b8327c59646284fa78c3c27e5490 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/0a76a8c765c7b8327c59646284fa78c3c27e5490 | * libtiff/tif_jpeg.c: validate BitsPerSample in JPEGSetupEncode() to avoid
undefined behaviour caused by invalid shift exponent.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2648 | 0 | JPEGSetupEncode(TIFF* tif)
{
JPEGState* sp = JState(tif);
TIFFDirectory *td = &tif->tif_dir;
static const char module[] = "JPEGSetupEncode";
#if defined(JPEG_DUAL_MODE_8_12) && !defined(TIFFInitJPEG)
if( tif->tif_dir.td_bitspersample == 12 )
return TIFFReInitJPEG_12( tif, COMPRESSION_JPEG, 1 );
... | 249,203,067,489,546,200,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2017-7601 | LibTIFF 4.0.7 has a "shift exponent too large for 64-bit type long" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted image. | https://nvd.nist.gov/vuln/detail/CVE-2017-7601 |
216,698 | libtiff | 69bfeec247899776b1b396651adb47436e5f1556 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/69bfeec247899776b1b396651adb47436e5f1556 | * tools/tiff2pdf.c: prevent heap buffer overflow write in "Raw"
mode on PlanarConfig=Contig input images.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2715
Reported by team OWL337 | 1 | void t2p_read_tiff_data(T2P* t2p, TIFF* input){
int i=0;
uint16* r;
uint16* g;
uint16* b;
uint16* a;
uint16 xuint16;
uint16* xuint16p;
float* xfloatp;
t2p->pdf_transcode = T2P_TRANSCODE_ENCODE;
t2p->pdf_sample = T2P_SAMPLE_NOTHING;
t2p->pdf_switchdecode = t2p->pdf_colorspace_invert;
TIFF... | 156,700,098,535,329,070,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2017-11335 | There is a heap based buffer overflow in tools/tiff2pdf.c of LibTIFF 4.0.8 via a PlanarConfig=Contig image, which causes a more than one hundred bytes out-of-bounds write (related to the ZIPDecode function in tif_zip.c). A crafted input may lead to a remote denial of service attack or an arbitrary code execution attack... | https://nvd.nist.gov/vuln/detail/CVE-2017-11335 |
504,510 | libtiff | 69bfeec247899776b1b396651adb47436e5f1556 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/69bfeec247899776b1b396651adb47436e5f1556 | * tools/tiff2pdf.c: prevent heap buffer overflow write in "Raw"
mode on PlanarConfig=Contig input images.
Fixes http://bugzilla.maptools.org/show_bug.cgi?id=2715
Reported by team OWL337 | 0 | void t2p_read_tiff_data(T2P* t2p, TIFF* input){
int i=0;
uint16* r;
uint16* g;
uint16* b;
uint16* a;
uint16 xuint16;
uint16* xuint16p;
float* xfloatp;
t2p->pdf_transcode = T2P_TRANSCODE_ENCODE;
t2p->pdf_sample = T2P_SAMPLE_NOTHING;
t2p->pdf_switchdecode = t2p->pdf_colorspace_invert;
TIFF... | 207,243,895,221,804,670,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2017-11335 | There is a heap based buffer overflow in tools/tiff2pdf.c of LibTIFF 4.0.8 via a PlanarConfig=Contig image, which causes a more than one hundred bytes out-of-bounds write (related to the ZIPDecode function in tif_zip.c). A crafted input may lead to a remote denial of service attack or an arbitrary code execution attack... | https://nvd.nist.gov/vuln/detail/CVE-2017-11335 |
216,699 | librsvg | ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | https://github.com/GNOME/librsvg | https://github.com/GNOME/librsvg/commit/ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | bgo#783835 - Don't divide by zero in box_blur_line() for gaussian blurs
We were making the decision to use box blurs, instead of a true
Gaussian kernel, based on the size of *both* x and y dimensions. Do
them individually instead. | 1 | box_blur_line (gint box_width, gint even_offset,
guchar *src, guchar *dest,
gint len, gint bpp)
{
gint i;
gint lead; /* This marks the leading edge of the kernel */
gint output; /* This marks the center of the kernel */
gint trail; ... | 254,965,085,204,809,130,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2017-11464 | A SIGFPE is raised in the function box_blur_line of rsvg-filter.c in GNOME librsvg 2.40.17 during an attempted parse of a crafted SVG file, because of incorrect protection against division by zero. | https://nvd.nist.gov/vuln/detail/CVE-2017-11464 |
504,588 | librsvg | ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | https://github.com/GNOME/librsvg | https://github.com/GNOME/librsvg/commit/ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | bgo#783835 - Don't divide by zero in box_blur_line() for gaussian blurs
We were making the decision to use box blurs, instead of a true
Gaussian kernel, based on the size of *both* x and y dimensions. Do
them individually instead. | 0 | box_blur_line (gint box_width, gint even_offset,
guchar *src, guchar *dest,
gint len, gint bpp)
{
gint i;
gint lead; /* This marks the leading edge of the kernel */
gint output; /* This marks the center of the kernel */
gint trail; ... | 314,447,498,710,656,830,000,000,000,000,000,000,000 | None | null | [
"CWE-369"
] | CVE-2017-11464 | A SIGFPE is raised in the function box_blur_line of rsvg-filter.c in GNOME librsvg 2.40.17 during an attempted parse of a crafted SVG file, because of incorrect protection against division by zero. | https://nvd.nist.gov/vuln/detail/CVE-2017-11464 |
216,708 | server | 0b5a5258abbeaf8a0c3a18c7e753699787fdf46e | https://github.com/MariaDB/server | https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e | MW-416 DDL replication moved after acl checking
galera_events test shows a regression with the original fix for MW-416
Reason was that Events::drop_event() can be called also from inside event
execution, and there we have a speacial treatment for event, which executes
"DROP EVENT" statement, and runs TOI replication i... | 1 | Event_job_data::execute(THD *thd, bool drop)
{
String sp_sql;
#ifndef NO_EMBEDDED_ACCESS_CHECKS
Security_context event_sctx, *save_sctx= NULL;
#endif
List<Item> empty_item_list;
bool ret= TRUE;
DBUG_ENTER("Event_job_data::execute");
thd->reset_for_next_command();
/*
MySQL parser currently assumes t... | 19,425,365,289,049,569,000,000,000,000,000,000,000 | None | null | [
"CWE-284"
] | CVE-2017-15365 | sql/event_data_objects.cc in MariaDB before 10.1.30 and 10.2.x before 10.2.10 and Percona XtraDB Cluster before 5.6.37-26.21-3 and 5.7.x before 5.7.19-29.22-3 allows remote authenticated users with SQL access to bypass intended access restrictions and replicate data definition language (DDL) statements to cluster nodes... | https://nvd.nist.gov/vuln/detail/CVE-2017-15365 |
505,165 | server | 0b5a5258abbeaf8a0c3a18c7e753699787fdf46e | https://github.com/MariaDB/server | https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e | MW-416 DDL replication moved after acl checking
galera_events test shows a regression with the original fix for MW-416
Reason was that Events::drop_event() can be called also from inside event
execution, and there we have a speacial treatment for event, which executes
"DROP EVENT" statement, and runs TOI replication i... | 0 | Event_job_data::execute(THD *thd, bool drop)
{
String sp_sql;
#ifndef NO_EMBEDDED_ACCESS_CHECKS
Security_context event_sctx, *save_sctx= NULL;
#endif
List<Item> empty_item_list;
bool ret= TRUE;
DBUG_ENTER("Event_job_data::execute");
thd->reset_for_next_command();
/*
MySQL parser currently assumes t... | 238,022,891,487,621,280,000,000,000,000,000,000,000 | None | null | [
"CWE-284"
] | CVE-2017-15365 | sql/event_data_objects.cc in MariaDB before 10.1.30 and 10.2.x before 10.2.10 and Percona XtraDB Cluster before 5.6.37-26.21-3 and 5.7.x before 5.7.19-29.22-3 allows remote authenticated users with SQL access to bypass intended access restrictions and replicate data definition language (DDL) statements to cluster nodes... | https://nvd.nist.gov/vuln/detail/CVE-2017-15365 |
216,721 | audiofile | 822b732fd31ffcb78f6920001e9b1fbd815fa712 | https://github.com/antlarr/audiofile | https://github.com/wtay/audiofile/commit/822b732fd31ffcb78f6920001e9b1fbd815fa712 | SimpleModule: set output chunk framecount after pull
After pulling the data, set the output chunk to the amount of
frames we pulled so that the next module in the chain has the correct
frame count.
Fixes #50 and #51 | 1 | void SimpleModule::runPull()
{
pull(m_outChunk->frameCount);
run(*m_inChunk, *m_outChunk);
} | 206,287,461,897,027,900,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-17095 | An issue has been discovered in mpruett Audio File Library (aka audiofile) 0.3.6, 0.3.5, 0.3.4, 0.3.3, 0.3.2, 0.3.1, 0.3.0. A heap-based buffer overflow in Expand3To4Module::run has occurred when running sfconvert. | https://nvd.nist.gov/vuln/detail/CVE-2018-17095 |
505,415 | audiofile | 822b732fd31ffcb78f6920001e9b1fbd815fa712 | https://github.com/antlarr/audiofile | https://github.com/wtay/audiofile/commit/822b732fd31ffcb78f6920001e9b1fbd815fa712 | SimpleModule: set output chunk framecount after pull
After pulling the data, set the output chunk to the amount of
frames we pulled so that the next module in the chain has the correct
frame count.
Fixes #50 and #51 | 0 | void SimpleModule::runPull()
{
pull(m_outChunk->frameCount);
m_outChunk->frameCount = m_inChunk->frameCount;
run(*m_inChunk, *m_outChunk);
} | 46,489,266,912,818,470,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2018-17095 | An issue has been discovered in mpruett Audio File Library (aka audiofile) 0.3.6, 0.3.5, 0.3.4, 0.3.3, 0.3.2, 0.3.1, 0.3.0. A heap-based buffer overflow in Expand3To4Module::run has occurred when running sfconvert. | https://nvd.nist.gov/vuln/detail/CVE-2018-17095 |
216,733 | core | 85fcb895ca7f0bcb8ee72047fe0e1e78532ff90b | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/85fcb895ca7f0bcb8ee72047fe0e1e78532ff90b | lib-imap: Don't accept strings with NULs
IMAP doesn't allow NULs except in binary literals. We'll still allow them
in regular literals as well, but just not in strings.
This fixes a bug with unescaping a string with NULs: str_unescape() could
have been called for memory that points outside the allocated string,
causi... | 1 | static bool imap_parser_read_string(struct imap_parser *parser,
const unsigned char *data, size_t data_size)
{
size_t i;
/* read until we've found non-escaped ", CR or LF */
for (i = parser->cur_pos; i < data_size; i++) {
if (data[i] == '"') {
imap_parser_save_arg(parser, data, i);
i++; /* skip the... | 72,163,637,243,327,820,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2019-11500 | In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings. This occurs because '\0' characters are mishandled, and can lead to out-of-bounds writes and remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-11500 |
505,558 | core | 85fcb895ca7f0bcb8ee72047fe0e1e78532ff90b | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/85fcb895ca7f0bcb8ee72047fe0e1e78532ff90b | lib-imap: Don't accept strings with NULs
IMAP doesn't allow NULs except in binary literals. We'll still allow them
in regular literals as well, but just not in strings.
This fixes a bug with unescaping a string with NULs: str_unescape() could
have been called for memory that points outside the allocated string,
causi... | 0 | static bool imap_parser_read_string(struct imap_parser *parser,
const unsigned char *data, size_t data_size)
{
size_t i;
/* read until we've found non-escaped ", CR or LF */
for (i = parser->cur_pos; i < data_size; i++) {
if (data[i] == '"') {
imap_parser_save_arg(parser, data, i);
i++; /* skip the... | 45,484,247,244,906,110,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2019-11500 | In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings. This occurs because '\0' characters are mishandled, and can lead to out-of-bounds writes and remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-11500 |
216,734 | core | f904cbdfec25582bc5e2a7435bf82ff769f2526a | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/f904cbdfec25582bc5e2a7435bf82ff769f2526a | lib-imap: Make sure str_unescape() won't be writing past allocated memory
The previous commit should already prevent this, but this makes sure it
can't become broken in the future either. It makes the performance a tiny
bit worse, but that's not practically noticeable. | 1 | static void imap_parser_save_arg(struct imap_parser *parser,
const unsigned char *data, size_t size)
{
struct imap_arg *arg;
char *str;
arg = imap_arg_create(parser);
switch (parser->cur_type) {
case ARG_PARSE_ATOM:
case ARG_PARSE_TEXT:
if (size == 3 && i_memcasecmp(data, "NIL", 3) == 0) {
/* NIL argu... | 260,817,611,865,611,240,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2019-11500 | In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings. This occurs because '\0' characters are mishandled, and can lead to out-of-bounds writes and remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-11500 |
505,580 | core | f904cbdfec25582bc5e2a7435bf82ff769f2526a | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/f904cbdfec25582bc5e2a7435bf82ff769f2526a | lib-imap: Make sure str_unescape() won't be writing past allocated memory
The previous commit should already prevent this, but this makes sure it
can't become broken in the future either. It makes the performance a tiny
bit worse, but that's not practically noticeable. | 0 | static void imap_parser_save_arg(struct imap_parser *parser,
const unsigned char *data, size_t size)
{
struct imap_arg *arg;
char *str;
arg = imap_arg_create(parser);
switch (parser->cur_type) {
case ARG_PARSE_ATOM:
case ARG_PARSE_TEXT:
if (size == 3 && i_memcasecmp(data, "NIL", 3) == 0) {
/* NIL argu... | 319,976,838,263,992,040,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2019-11500 | In Dovecot before 2.2.36.4 and 2.3.x before 2.3.7.2 (and Pigeonhole before 0.5.7.2), protocol processing can fail for quoted strings. This occurs because '\0' characters are mishandled, and can lead to out-of-bounds writes and remote code execution. | https://nvd.nist.gov/vuln/detail/CVE-2019-11500 |
216,763 | libssh | 391c78de9d0f7baec3a44d86a76f4e1324eb9529 | http://git.libssh.org/projects/libssh | https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.8&id=391c78de9d0f7baec3a44d86a76f4e1324eb9529 | CVE-2019-14889: scp: Don't allow file path longer than 32kb
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
Reviewed-by: Jakub Jelen <jjelen@redhat.com>
(cherry picked from commit 0b5ee397260b6e08dffa2c1ce515a153aaeda765) | 1 | ssh_scp ssh_scp_new(ssh_session session, int mode, const char *location)
{
ssh_scp scp = NULL;
if (session == NULL) {
goto error;
}
scp = (ssh_scp)calloc(1, sizeof(struct ssh_scp_struct));
if (scp == NULL) {
ssh_set_error(session, SSH_FATAL,
"Error allocating ... | 269,875,538,843,675,100,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-14889 | A flaw was found with the libssh API function ssh_scp_new() in versions before 0.9.3 and before 0.8.8. When the libssh SCP client connects to a server, the scp command, which includes a user-provided path, is executed on the server-side. In case the library is used in a way where users can influence the third parameter... | https://nvd.nist.gov/vuln/detail/CVE-2019-14889 |
505,640 | libssh | 391c78de9d0f7baec3a44d86a76f4e1324eb9529 | http://git.libssh.org/projects/libssh | https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.8&id=391c78de9d0f7baec3a44d86a76f4e1324eb9529 | CVE-2019-14889: scp: Don't allow file path longer than 32kb
Signed-off-by: Andreas Schneider <asn@cryptomilk.org>
Reviewed-by: Jakub Jelen <jjelen@redhat.com>
(cherry picked from commit 0b5ee397260b6e08dffa2c1ce515a153aaeda765) | 0 | ssh_scp ssh_scp_new(ssh_session session, int mode, const char *location)
{
ssh_scp scp = NULL;
if (session == NULL) {
goto error;
}
scp = (ssh_scp)calloc(1, sizeof(struct ssh_scp_struct));
if (scp == NULL) {
ssh_set_error(session, SSH_FATAL,
"Error allocating ... | 286,788,993,408,247,450,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-14889 | A flaw was found with the libssh API function ssh_scp_new() in versions before 0.9.3 and before 0.8.8. When the libssh SCP client connects to a server, the scp command, which includes a user-provided path, is executed on the server-side. In case the library is used in a way where users can influence the third parameter... | https://nvd.nist.gov/vuln/detail/CVE-2019-14889 |
216,764 | libssh | b0edec4e8d01ad73b0d26ad4070d7e1a1e86dfc8 | http://git.libssh.org/projects/libssh | https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.8&id=b0edec4e8d01ad73b0d26ad4070d7e1a1e86dfc8 | CVE-2019-14889: scp: Quote location to be used on shell
Single quote file paths to be used on commands to be executed on remote
shell.
Fixes T181
Signed-off-by: Anderson Toshiyuki Sasaki <ansasaki@redhat.com>
Reviewed-by: Andreas Schneider <asn@cryptomilk.org>
(cherry picked from commit 3830c7ae6eec751b7618d3fc159cb... | 1 | int ssh_scp_init(ssh_scp scp)
{
int rc;
char execbuffer[1024] = {0};
if (scp == NULL) {
return SSH_ERROR;
}
if (scp->state != SSH_SCP_NEW) {
ssh_set_error(scp->session, SSH_FATAL,
"ssh_scp_init called under invalid state");
return SSH_ERROR;
}
... | 22,339,764,478,984,946,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-14889 | A flaw was found with the libssh API function ssh_scp_new() in versions before 0.9.3 and before 0.8.8. When the libssh SCP client connects to a server, the scp command, which includes a user-provided path, is executed on the server-side. In case the library is used in a way where users can influence the third parameter... | https://nvd.nist.gov/vuln/detail/CVE-2019-14889 |
505,641 | libssh | b0edec4e8d01ad73b0d26ad4070d7e1a1e86dfc8 | http://git.libssh.org/projects/libssh | https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.8&id=b0edec4e8d01ad73b0d26ad4070d7e1a1e86dfc8 | CVE-2019-14889: scp: Quote location to be used on shell
Single quote file paths to be used on commands to be executed on remote
shell.
Fixes T181
Signed-off-by: Anderson Toshiyuki Sasaki <ansasaki@redhat.com>
Reviewed-by: Andreas Schneider <asn@cryptomilk.org>
(cherry picked from commit 3830c7ae6eec751b7618d3fc159cb... | 0 | int ssh_scp_init(ssh_scp scp)
{
int rc;
char execbuffer[1024] = {0};
char *quoted_location = NULL;
size_t quoted_location_len = 0;
size_t scp_location_len;
if (scp == NULL) {
return SSH_ERROR;
}
if (scp->state != SSH_SCP_NEW) {
ssh_set_error(scp->session, SSH_FATAL,
... | 227,630,105,393,865,700,000,000,000,000,000,000,000 | None | null | [
"CWE-78"
] | CVE-2019-14889 | A flaw was found with the libssh API function ssh_scp_new() in versions before 0.9.3 and before 0.8.8. When the libssh SCP client connects to a server, the scp command, which includes a user-provided path, is executed on the server-side. In case the library is used in a way where users can influence the third parameter... | https://nvd.nist.gov/vuln/detail/CVE-2019-14889 |
216,768 | core | 3a55f35c208b5fd3d52c0a6272bd5b8717a2ae54 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/3a55f35c208b5fd3d52c0a6272bd5b8717a2ae54 | lib-mail: message_snippet_generate() - Fix potential crash when input ends with '>'
This happens only when the mail was large enough and full enough with
whitespace that message-parser returned multiple blocks before the snippet
was finished.
Broken by 74063ed8219d055489d5233b0c02a59886d2078c | 1 | static void snippet_add_content(struct snippet_context *ctx,
struct snippet_data *target,
const unsigned char *data, size_t size,
size_t *count_r)
{
i_assert(target != NULL);
if (size >= 3 &&
((data[0] == 0xEF && data[1] == 0xBB && data[2] == 0xBF) ||
(data[0] == 0xBF && data[1] == 0xBB && da... | 175,798,702,391,280,870,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-7957 | The IMAP and LMTP components in Dovecot 2.3.9 before 2.3.9.3 mishandle snippet generation when many characters must be read to compute the snippet and a trailing > character exists. This causes a denial of service in which the recipient cannot read all of their messages. | https://nvd.nist.gov/vuln/detail/CVE-2020-7957 |
505,663 | core | 3a55f35c208b5fd3d52c0a6272bd5b8717a2ae54 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/3a55f35c208b5fd3d52c0a6272bd5b8717a2ae54 | lib-mail: message_snippet_generate() - Fix potential crash when input ends with '>'
This happens only when the mail was large enough and full enough with
whitespace that message-parser returned multiple blocks before the snippet
was finished.
Broken by 74063ed8219d055489d5233b0c02a59886d2078c | 0 | static void snippet_add_content(struct snippet_context *ctx,
struct snippet_data *target,
const unsigned char *data, size_t size,
size_t *count_r)
{
i_assert(target != NULL);
if (size == 0)
return;
if (size >= 3 &&
((data[0] == 0xEF && data[1] == 0xBB && data[2] == 0xBF) ||
(data[0] == 0xB... | 158,289,765,351,447,300,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-7957 | The IMAP and LMTP components in Dovecot 2.3.9 before 2.3.9.3 mishandle snippet generation when many characters must be read to compute the snippet and a trailing > character exists. This causes a denial of service in which the recipient cannot read all of their messages. | https://nvd.nist.gov/vuln/detail/CVE-2020-7957 |
216,777 | openssl | a87f3fe01a5a894aa27ccd6a239155fd129988e4 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/a87f3fe01a5a894aa27ccd6a239155fd129988e4 | Fix NULL dereference in SSL_check_chain() for TLS 1.3
In the tls1_check_sig_alg() helper function, we loop through the list of
"signature_algorithms_cert" values received from the client and attempt
to look up each one in turn in our internal table that maps wire
codepoint to string-form name, digest and/or signature ... | 1 | static int tls1_check_sig_alg(SSL *s, X509 *x, int default_nid)
{
int sig_nid, use_pc_sigalgs = 0;
size_t i;
const SIGALG_LOOKUP *sigalg;
size_t sigalgslen;
if (default_nid == -1)
return 1;
sig_nid = X509_get_signature_nid(x);
if (default_nid)
return sig_nid == default_nid ? ... | 277,027,437,880,374,400,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1967 | Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from t... | https://nvd.nist.gov/vuln/detail/CVE-2020-1967 |
505,978 | openssl | a87f3fe01a5a894aa27ccd6a239155fd129988e4 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/a87f3fe01a5a894aa27ccd6a239155fd129988e4 | Fix NULL dereference in SSL_check_chain() for TLS 1.3
In the tls1_check_sig_alg() helper function, we loop through the list of
"signature_algorithms_cert" values received from the client and attempt
to look up each one in turn in our internal table that maps wire
codepoint to string-form name, digest and/or signature ... | 0 | static int tls1_check_sig_alg(SSL *s, X509 *x, int default_nid)
{
int sig_nid, use_pc_sigalgs = 0;
size_t i;
const SIGALG_LOOKUP *sigalg;
size_t sigalgslen;
if (default_nid == -1)
return 1;
sig_nid = X509_get_signature_nid(x);
if (default_nid)
return sig_nid == default_nid ? ... | 197,374,734,987,327,100,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1967 | Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from t... | https://nvd.nist.gov/vuln/detail/CVE-2020-1967 |
216,805 | openssl | 3db2c9f3e5fb9f649ebb4a55918398756310af43 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/3db2c9f3e5fb9f649ebb4a55918398756310af43 | Complain if we are attempting to encode with an invalid ASN.1 template
It never makes sense for multi-string or CHOICE types to have implicit
tagging. If we have a template that uses the in this way then we
should immediately fail.
Thanks to David Benjamin from Google for reporting this issue.
Reviewed-by: Tomas Mra... | 1 | int ASN1_item_ex_i2d(const ASN1_VALUE **pval, unsigned char **out,
const ASN1_ITEM *it, int tag, int aclass)
{
const ASN1_TEMPLATE *tt = NULL;
int i, seqcontlen, seqlen, ndef = 1;
const ASN1_EXTERN_FUNCS *ef;
const ASN1_AUX *aux = it->funcs;
ASN1_aux_const_cb *asn1_cb = NULL;
... | 200,049,814,984,067,160,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
506,633 | openssl | 3db2c9f3e5fb9f649ebb4a55918398756310af43 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/3db2c9f3e5fb9f649ebb4a55918398756310af43 | Complain if we are attempting to encode with an invalid ASN.1 template
It never makes sense for multi-string or CHOICE types to have implicit
tagging. If we have a template that uses the in this way then we
should immediately fail.
Thanks to David Benjamin from Google for reporting this issue.
Reviewed-by: Tomas Mra... | 0 | int ASN1_item_ex_i2d(const ASN1_VALUE **pval, unsigned char **out,
const ASN1_ITEM *it, int tag, int aclass)
{
const ASN1_TEMPLATE *tt = NULL;
int i, seqcontlen, seqlen, ndef = 1;
const ASN1_EXTERN_FUNCS *ef;
const ASN1_AUX *aux = it->funcs;
ASN1_aux_const_cb *asn1_cb = NULL;
... | 218,749,472,589,691,270,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
216,806 | openssl | 43a7033a010feaf72c79d39df65ca733fb9dcd4c | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/43a7033a010feaf72c79d39df65ca733fb9dcd4c | Check that multi-strings/CHOICE types don't use implicit tagging
It never makes sense for multi-string or CHOICE types to use implicit
tagging since the content would be ambiguous. It is an error in the
template if this ever happens. If we detect it we should stop parsing.
Thanks to David Benjamin from Google for rep... | 1 | static int asn1_item_embed_d2i(ASN1_VALUE **pval, const unsigned char **in,
long len, const ASN1_ITEM *it,
int tag, int aclass, char opt, ASN1_TLC *ctx,
int depth)
{
const ASN1_TEMPLATE *tt, *errtt = NULL;
const ASN1_EX... | 228,491,106,940,238,130,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
506,643 | openssl | 43a7033a010feaf72c79d39df65ca733fb9dcd4c | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/43a7033a010feaf72c79d39df65ca733fb9dcd4c | Check that multi-strings/CHOICE types don't use implicit tagging
It never makes sense for multi-string or CHOICE types to use implicit
tagging since the content would be ambiguous. It is an error in the
template if this ever happens. If we detect it we should stop parsing.
Thanks to David Benjamin from Google for rep... | 0 | static int asn1_item_embed_d2i(ASN1_VALUE **pval, const unsigned char **in,
long len, const ASN1_ITEM *it,
int tag, int aclass, char opt, ASN1_TLC *ctx,
int depth)
{
const ASN1_TEMPLATE *tt, *errtt = NULL;
const ASN1_EX... | 220,658,367,577,115,750,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
216,808 | openssl | b33c48b75aaf33c93aeda42d7138616b9e6a64cb | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/b33c48b75aaf33c93aeda42d7138616b9e6a64cb | Correctly compare EdiPartyName in GENERAL_NAME_cmp()
If a GENERAL_NAME field contained EdiPartyName data then it was
incorrectly being handled as type "other". This could lead to a
segmentation fault.
Many thanks to David Benjamin from Google for reporting this issue.
CVE-2020-1971
Reviewed-by: Tomas Mraz <tmraz@fe... | 1 | int GENERAL_NAME_cmp(GENERAL_NAME *a, GENERAL_NAME *b)
{
int result = -1;
if (!a || !b || a->type != b->type)
return -1;
switch (a->type) {
case GEN_X400:
case GEN_EDIPARTY:
result = ASN1_TYPE_cmp(a->d.other, b->d.other);
break;
case GEN_OTHERNAME:
result = OTHE... | 13,470,328,887,014,610,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
506,651 | openssl | b33c48b75aaf33c93aeda42d7138616b9e6a64cb | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/b33c48b75aaf33c93aeda42d7138616b9e6a64cb | Correctly compare EdiPartyName in GENERAL_NAME_cmp()
If a GENERAL_NAME field contained EdiPartyName data then it was
incorrectly being handled as type "other". This could lead to a
segmentation fault.
Many thanks to David Benjamin from Google for reporting this issue.
CVE-2020-1971
Reviewed-by: Tomas Mraz <tmraz@fe... | 0 | int GENERAL_NAME_cmp(GENERAL_NAME *a, GENERAL_NAME *b)
{
int result = -1;
if (!a || !b || a->type != b->type)
return -1;
switch (a->type) {
case GEN_X400:
result = ASN1_TYPE_cmp(a->d.x400Address, b->d.x400Address);
break;
case GEN_EDIPARTY:
result = edipartyname_cmp... | 140,642,209,321,295,110,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2020-1971 | The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL... | https://nvd.nist.gov/vuln/detail/CVE-2020-1971 |
216,814 | core | 266e54b7b8c34c9a58dd60a2e53c5ca7d1deae19 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/266e54b7b8c34c9a58dd60a2e53c5ca7d1deae19 | lib-imap: Don't generate invalid BODYSTRUCTURE when reaching MIME part limit
If the last MIME part was message/rfc822 and its child was truncated away,
BODYSTRUCTURE was missing the ENVELOPE and BODY[STRUCTURE] parts. Fixed by
writing empty dummy ones. | 1 | static void part_write_body(const struct message_part *part,
string_t *str, bool extended)
{
const struct message_part_data *data = part->data;
bool text;
i_assert(part->data != NULL);
if ((part->flags & MESSAGE_PART_FLAG_MESSAGE_RFC822) != 0) {
str_append(str, "\"message\" \"rfc822\"");
text = FALSE;
... | 295,789,678,778,666,360,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-25275 | Dovecot before 2.3.13 has Improper Input Validation in lda, lmtp, and imap, leading to an application crash via a crafted email message with certain choices for ten thousand MIME parts. | https://nvd.nist.gov/vuln/detail/CVE-2020-25275 |
506,746 | core | 266e54b7b8c34c9a58dd60a2e53c5ca7d1deae19 | https://github.com/LibreOffice/core | https://github.com/dovecot/core/commit/266e54b7b8c34c9a58dd60a2e53c5ca7d1deae19 | lib-imap: Don't generate invalid BODYSTRUCTURE when reaching MIME part limit
If the last MIME part was message/rfc822 and its child was truncated away,
BODYSTRUCTURE was missing the ENVELOPE and BODY[STRUCTURE] parts. Fixed by
writing empty dummy ones. | 0 | static void part_write_body(const struct message_part *part,
string_t *str, bool extended)
{
const struct message_part_data *data = part->data;
bool text, message_rfc822;
i_assert(part->data != NULL);
if ((part->flags & MESSAGE_PART_FLAG_MESSAGE_RFC822) != 0)
message_rfc822 = TRUE;
else if (data->conten... | 221,225,704,223,118,700,000,000,000,000,000,000,000 | None | null | [
"CWE-20"
] | CVE-2020-25275 | Dovecot before 2.3.13 has Improper Input Validation in lda, lmtp, and imap, leading to an application crash via a crafted email message with certain choices for ten thousand MIME parts. | https://nvd.nist.gov/vuln/detail/CVE-2020-25275 |
216,817 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | int Http2Stream::DoWrite(WriteWrap* req_wrap,
uv_buf_t* bufs,
size_t nbufs,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
Http2Scope h2scope(this);
if (!IsWritable() || IsDestroyed()) {
req_wrap->Done(UV_EOF);
return 0;
}
... | 75,575,285,253,214,080,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
506,890 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | int Http2Stream::DoWrite(std::unique_ptr<WriteWrap>& req_wrap,
uv_buf_t* bufs,
size_t nbufs,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
Http2Scope h2scope(this);
if (!IsWritable() || IsDestroyed()) {
req_wrap->Done(UV_EOF);
... | 39,206,109,051,228,437,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,819 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | int DoWrite(WriteWrap* w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) override {
return UV_ENOSYS; // Not implemented (yet).
} | 97,371,337,468,241,030,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
506,991 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | int DoWrite(std::unique_ptr<WriteWrap>& w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) override {
return UV_ENOSYS; // Not implemented (yet).
} | 258,097,183,119,728,600,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,820 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | int JSStream::DoWrite(WriteWrap* w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
HandleScope scope(env()->isolate());
Context::Scope context_scope(env()->context());
Local<Array> bufs_arr = Array::New(env()... | 296,528,058,089,687,640,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
507,020 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | int JSStream::DoWrite(std::unique_ptr<WriteWrap>& w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
HandleScope scope(env()->isolate());
Context::Scope context_scope(env()->context());
Local<Array> bufs_arr =... | 336,539,999,664,597,800,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,821 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | int LibuvStreamWrap::DoWrite(WriteWrap* req_wrap,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
LibuvWriteWrap* w = static_cast<LibuvWriteWrap*>(req_wrap);
int r;
if (send_handle == nullptr) {
r = w->Dispatch(uv... | 110,676,424,097,614,400,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
507,040 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | int LibuvStreamWrap::DoWrite(std::unique_ptr<WriteWrap>& req_wrap,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
LibuvWriteWrap* w = static_cast<LibuvWriteWrap*>(req_wrap.get());
int r;
if (send_handle == nullptr) {... | 202,966,899,678,784,040,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,822 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | inline StreamWriteResult StreamBase::Write(
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle,
v8::Local<v8::Object> req_wrap_obj) {
Environment* env = stream_env();
int err;
size_t total_bytes = 0;
for (size_t i = 0; i < count; ++i)
total_bytes += bufs[i].len;
bytes_written_ += tota... | 33,944,571,286,802,694,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
506,891 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | inline StreamWriteResult StreamBase::Write(
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle,
v8::Local<v8::Object> req_wrap_obj) {
Environment* env = stream_env();
int err;
size_t total_bytes = 0;
for (size_t i = 0; i < count; ++i)
total_bytes += bufs[i].len;
bytes_written_ += tota... | 156,567,598,039,850,740,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,823 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 1 | int TLSWrap::DoWrite(WriteWrap* w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
Debug(this, "DoWrite()");
if (ssl_ == nullptr) {
ClearError();
error_ = "Write after DestroySSL";
return UV_EPROTO;
}
... | 312,457,013,437,732,140,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
506,856 | node | 7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | https://github.com/joyent/node | https://github.com/nodejs/node/commit/7f178663ebffc82c9f8a5a1b6bf2da0c263a30ed | src: use unique_ptr for WriteWrap
This commit attempts to avoid a use-after-free error by using unqiue_ptr
and passing a reference to it.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
PR-URL: https://github.com/nodejs-private/node-private/pull/238
Reviewed-By: Michael Dawson <... | 0 | int TLSWrap::DoWrite(std::unique_ptr<WriteWrap>& w,
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle) {
CHECK_NULL(send_handle);
Debug(this, "DoWrite()");
if (ssl_ == nullptr) {
ClearError();
error_ = "Write after DestroySSL";
retur... | 247,852,876,199,201,220,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,825 | node | 4f8772f9b731118628256189b73cd202149bbd97 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/4f8772f9b731118628256189b73cd202149bbd97 | src: retain pointers to WriteWrap/ShutdownWrap
Avoids potential use-after-free when wrap req's are synchronously
destroyed.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
Refs: https://hackerone.com/bugs?subject=nodejs&report_id=988103
PR-URL: https://github.com/nodejs-private/... | 1 | StreamWriteResult StreamBase::Write(
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle,
v8::Local<v8::Object> req_wrap_obj) {
Environment* env = stream_env();
int err;
size_t total_bytes = 0;
for (size_t i = 0; i < count; ++i)
total_bytes += bufs[i].len;
bytes_written_ += total_bytes... | 76,699,292,629,144,670,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
507,120 | node | 4f8772f9b731118628256189b73cd202149bbd97 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/4f8772f9b731118628256189b73cd202149bbd97 | src: retain pointers to WriteWrap/ShutdownWrap
Avoids potential use-after-free when wrap req's are synchronously
destroyed.
CVE-ID: CVE-2020-8265
Fixes: https://github.com/nodejs-private/node-private/issues/227
Refs: https://hackerone.com/bugs?subject=nodejs&report_id=988103
PR-URL: https://github.com/nodejs-private/... | 0 | StreamWriteResult StreamBase::Write(
uv_buf_t* bufs,
size_t count,
uv_stream_t* send_handle,
v8::Local<v8::Object> req_wrap_obj) {
Environment* env = stream_env();
int err;
size_t total_bytes = 0;
for (size_t i = 0; i < count; ++i)
total_bytes += bufs[i].len;
bytes_written_ += total_bytes... | 69,224,095,910,162,280,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2020-8265 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an err... | https://nvd.nist.gov/vuln/detail/CVE-2020-8265 |
216,829 | node | fc70ce08f5818a286fb5899a1bc3aff5965a745e | https://github.com/joyent/node | https://github.com/nodejs/node/commit/fc70ce08f5818a286fb5899a1bc3aff5965a745e | http: unset `F_CHUNKED` on new `Transfer-Encoding`
Duplicate `Transfer-Encoding` header should be a treated as a single,
but with original header values concatenated with a comma separator. In
the light of this, even if the past `Transfer-Encoding` ended with
`chunked`, we should be not let the `F_CHUNKED` to leak int... | 1 |
size_t http_parser_execute (http_parser *parser,
const http_parser_settings *settings,
const char *data,
size_t len)
{
char c, ch;
int8_t unhex_val;
const char *p = data;
const char *header_field_mark = 0;
const char *header_... | 319,662,195,661,461,750,000,000,000,000,000,000,000 | None | null | [
"CWE-444"
] | CVE-2020-8287 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling. | https://nvd.nist.gov/vuln/detail/CVE-2020-8287 |
507,185 | node | fc70ce08f5818a286fb5899a1bc3aff5965a745e | https://github.com/joyent/node | https://github.com/nodejs/node/commit/fc70ce08f5818a286fb5899a1bc3aff5965a745e | http: unset `F_CHUNKED` on new `Transfer-Encoding`
Duplicate `Transfer-Encoding` header should be a treated as a single,
but with original header values concatenated with a comma separator. In
the light of this, even if the past `Transfer-Encoding` ended with
`chunked`, we should be not let the `F_CHUNKED` to leak int... | 0 |
size_t http_parser_execute (http_parser *parser,
const http_parser_settings *settings,
const char *data,
size_t len)
{
char c, ch;
int8_t unhex_val;
const char *p = data;
const char *header_field_mark = 0;
const char *header_... | 315,130,984,024,133,230,000,000,000,000,000,000,000 | None | null | [
"CWE-444"
] | CVE-2020-8287 | Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling. | https://nvd.nist.gov/vuln/detail/CVE-2020-8287 |
216,830 | openssl | 901f1ef7dacb6b3bde63233a1f623e1fa2f0f058 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/901f1ef7dacb6b3bde63233a1f623e1fa2f0f058 | Fix the RSA_SSLV23_PADDING padding type
This also fixes the public function RSA_padding_check_SSLv23.
Commit 6555a89 changed the padding check logic in RSA_padding_check_SSLv23
so that padding is rejected if the nul delimiter byte is not immediately
preceded by at least 8 bytes containing 0x03. Prior to that commit t... | 1 | int RSA_padding_check_SSLv23(unsigned char *to, int tlen,
const unsigned char *from, int flen, int num)
{
int i;
/* |em| is the encoded message, zero-padded to exactly |num| bytes */
unsigned char *em = NULL;
unsigned int good, found_zero_byte, mask, threes_in_row;
int z... | 140,900,912,367,715,020,000,000,000,000,000,000,000 | None | null | [
"CWE-326"
] | CVE-2021-23839 | OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed t... | https://nvd.nist.gov/vuln/detail/CVE-2021-23839 |
507,189 | openssl | 901f1ef7dacb6b3bde63233a1f623e1fa2f0f058 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/901f1ef7dacb6b3bde63233a1f623e1fa2f0f058 | Fix the RSA_SSLV23_PADDING padding type
This also fixes the public function RSA_padding_check_SSLv23.
Commit 6555a89 changed the padding check logic in RSA_padding_check_SSLv23
so that padding is rejected if the nul delimiter byte is not immediately
preceded by at least 8 bytes containing 0x03. Prior to that commit t... | 0 | int RSA_padding_check_SSLv23(unsigned char *to, int tlen,
const unsigned char *from, int flen, int num)
{
int i;
/* |em| is the encoded message, zero-padded to exactly |num| bytes */
unsigned char *em = NULL;
unsigned int good, found_zero_byte, mask, threes_in_row;
int z... | 209,387,595,545,725,800,000,000,000,000,000,000,000 | None | null | [
"CWE-326"
] | CVE-2021-23839 | OpenSSL 1.0.2 supports SSLv2. If a client attempts to negotiate SSLv2 with a server that is configured to support both SSLv2 and more recent SSL and TLS versions then a check is made for a version rollback attack when unpadding an RSA signature. Clients that support SSL or TLS versions greater than SSLv2 are supposed t... | https://nvd.nist.gov/vuln/detail/CVE-2021-23839 |
216,831 | openssl | 8130d654d1de922ea224fa18ee3bc7262edc39c0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/8130d654d1de922ea224fa18ee3bc7262edc39c0 | Fix Null pointer deref in X509_issuer_and_serial_hash()
The OpenSSL public API function X509_issuer_and_serial_hash() attempts
to create a unique hash value based on the issuer and serial number data
contained within an X509 certificate. However it fails to correctly
handle any errors that may occur while parsing the ... | 1 | unsigned long X509_issuer_and_serial_hash(X509 *a)
{
unsigned long ret = 0;
EVP_MD_CTX *ctx = EVP_MD_CTX_new();
unsigned char md[16];
char *f;
if (ctx == NULL)
goto err;
f = X509_NAME_oneline(a->cert_info.issuer, NULL, 0);
if (!EVP_DigestInit_ex(ctx, EVP_md5(), NULL))
goto e... | 224,899,248,177,107,330,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-23841 | The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is ma... | https://nvd.nist.gov/vuln/detail/CVE-2021-23841 |
507,205 | openssl | 8130d654d1de922ea224fa18ee3bc7262edc39c0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/8130d654d1de922ea224fa18ee3bc7262edc39c0 | Fix Null pointer deref in X509_issuer_and_serial_hash()
The OpenSSL public API function X509_issuer_and_serial_hash() attempts
to create a unique hash value based on the issuer and serial number data
contained within an X509 certificate. However it fails to correctly
handle any errors that may occur while parsing the ... | 0 | unsigned long X509_issuer_and_serial_hash(X509 *a)
{
unsigned long ret = 0;
EVP_MD_CTX *ctx = EVP_MD_CTX_new();
unsigned char md[16];
char *f;
if (ctx == NULL)
goto err;
f = X509_NAME_oneline(a->cert_info.issuer, NULL, 0);
if (f == NULL)
goto err;
if (!EVP_DigestInit_ex(... | 128,383,710,510,994,940,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-23841 | The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is ma... | https://nvd.nist.gov/vuln/detail/CVE-2021-23841 |
216,832 | openssl | 55869f594f052561b11a2db6a7c42690051868de | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/55869f594f052561b11a2db6a7c42690051868de | Test that X509_issuer_and_serial_hash doesn't crash
Provide a certificate with a bad issuer and check that
X509_issuer_and_serial_hash doesn't crash.
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | int FuzzerTestOneInput(const uint8_t *buf, size_t len)
{
const unsigned char *p = buf;
unsigned char *der = NULL;
X509 *x509 = d2i_X509(NULL, &p, len);
if (x509 != NULL) {
BIO *bio = BIO_new(BIO_s_null());
/* This will load and print the public key as well as extensions */
X509_... | 324,524,148,376,545,030,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-23841 | The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is ma... | https://nvd.nist.gov/vuln/detail/CVE-2021-23841 |
507,223 | openssl | 55869f594f052561b11a2db6a7c42690051868de | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/55869f594f052561b11a2db6a7c42690051868de | Test that X509_issuer_and_serial_hash doesn't crash
Provide a certificate with a bad issuer and check that
X509_issuer_and_serial_hash doesn't crash.
Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | int FuzzerTestOneInput(const uint8_t *buf, size_t len)
{
const unsigned char *p = buf;
unsigned char *der = NULL;
X509 *x509 = d2i_X509(NULL, &p, len);
if (x509 != NULL) {
BIO *bio = BIO_new(BIO_s_null());
/* This will load and print the public key as well as extensions */
X509_... | 38,148,017,826,076,580,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-23841 | The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing the issuer field (which might occur if the issuer field is ma... | https://nvd.nist.gov/vuln/detail/CVE-2021-23841 |
216,833 | openssl | 6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1 | Don't overflow the output length in EVP_CipherUpdate calls
CVE-2021-23840
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | int EVP_DecryptUpdate(EVP_CIPHER_CTX *ctx, unsigned char *out, int *outl,
const unsigned char *in, int inl)
{
int fix_len, cmpl = inl;
unsigned int b;
/* Prevent accidental use of encryption context when decrypting */
if (ctx->encrypt) {
EVPerr(EVP_F_EVP_DECRYPTUPDATE, EVP... | 143,552,303,372,982,300,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2021-23840 | Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output ... | https://nvd.nist.gov/vuln/detail/CVE-2021-23840 |
507,234 | openssl | 6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/6a51b9e1d0cf0bf8515f7201b68fb0a3482b3dc1 | Don't overflow the output length in EVP_CipherUpdate calls
CVE-2021-23840
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | int EVP_DecryptUpdate(EVP_CIPHER_CTX *ctx, unsigned char *out, int *outl,
const unsigned char *in, int inl)
{
int fix_len, cmpl = inl;
unsigned int b;
/* Prevent accidental use of encryption context when decrypting */
if (ctx->encrypt) {
EVPerr(EVP_F_EVP_DECRYPTUPDATE, EVP... | 84,755,923,943,046,670,000,000,000,000,000,000,000 | None | null | [
"CWE-190"
] | CVE-2021-23840 | Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output ... | https://nvd.nist.gov/vuln/detail/CVE-2021-23840 |
216,837 | openssl | fb9fa6b51defd48157eeb207f52181f735d96148 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/fb9fa6b51defd48157eeb207f52181f735d96148 | ssl sigalg extension: fix NULL pointer dereference
As the variable peer_sigalgslen is not cleared on ssl rehandshake, it's
possible to crash an openssl tls secured server remotely by sending a
manipulated hello message in a rehandshake.
On such a manipulated rehandshake, tls1_set_shared_sigalgs() calls
tls12_shared_s... | 1 | static int init_sig_algs(SSL *s, unsigned int context)
{
/* Clear any signature algorithms extension received */
OPENSSL_free(s->s3->tmp.peer_sigalgs);
s->s3->tmp.peer_sigalgs = NULL;
return 1;
} | 188,938,055,007,690,530,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-3449 | An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer derefer... | https://nvd.nist.gov/vuln/detail/CVE-2021-3449 |
507,338 | openssl | fb9fa6b51defd48157eeb207f52181f735d96148 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/fb9fa6b51defd48157eeb207f52181f735d96148 | ssl sigalg extension: fix NULL pointer dereference
As the variable peer_sigalgslen is not cleared on ssl rehandshake, it's
possible to crash an openssl tls secured server remotely by sending a
manipulated hello message in a rehandshake.
On such a manipulated rehandshake, tls1_set_shared_sigalgs() calls
tls12_shared_s... | 0 | static int init_sig_algs_cert(SSL *s, unsigned int context)
{
/* Clear any signature algorithms extension received */
OPENSSL_free(s->s3->tmp.peer_cert_sigalgs);
s->s3->tmp.peer_cert_sigalgs = NULL;
return 1;
} | 65,373,578,696,605,080,000,000,000,000,000,000,000 | None | null | [
"CWE-476"
] | CVE-2021-3449 | An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer derefer... | https://nvd.nist.gov/vuln/detail/CVE-2021-3449 |
216,838 | qemu | defac5e2fbddf8423a354ff0454283a2115e1367 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/defac5e2fbddf8423a354ff0454283a2115e1367 | hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507)
Per the 82078 datasheet, if the end-of-track (EOT byte in
the FIFO) is more than the number of sectors per side, the
command is terminated unsuccessfully:
* 5.2.5 DATA TRANSFER TERMINATION
The 82078 supports terminal count explicitly through
the TC pin a... | 1 | static void fdctrl_start_transfer(FDCtrl *fdctrl, int direction)
{
FDrive *cur_drv;
uint8_t kh, kt, ks;
SET_CUR_DRV(fdctrl, fdctrl->fifo[1] & FD_DOR_SELMASK);
cur_drv = get_cur_drv(fdctrl);
kt = fdctrl->fifo[2];
kh = fdctrl->fifo[3];
ks = fdctrl->fifo[4];
FLOPPY_DPRINTF("Start transfer ... | 27,909,349,407,897,200,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2021-3507 | A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). It could occur in fdctrl_transfer_handler() in hw/block/fdc.c while processing DMA read data transfers from the floppy drive to the guest system. A privileged guest user could use this flaw to crash the QEMU process on the hos... | https://nvd.nist.gov/vuln/detail/CVE-2021-3507 |
507,394 | qemu | defac5e2fbddf8423a354ff0454283a2115e1367 | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/defac5e2fbddf8423a354ff0454283a2115e1367 | hw/block/fdc: Prevent end-of-track overrun (CVE-2021-3507)
Per the 82078 datasheet, if the end-of-track (EOT byte in
the FIFO) is more than the number of sectors per side, the
command is terminated unsuccessfully:
* 5.2.5 DATA TRANSFER TERMINATION
The 82078 supports terminal count explicitly through
the TC pin a... | 0 | static void fdctrl_start_transfer(FDCtrl *fdctrl, int direction)
{
FDrive *cur_drv;
uint8_t kh, kt, ks;
SET_CUR_DRV(fdctrl, fdctrl->fifo[1] & FD_DOR_SELMASK);
cur_drv = get_cur_drv(fdctrl);
kt = fdctrl->fifo[2];
kh = fdctrl->fifo[3];
ks = fdctrl->fifo[4];
FLOPPY_DPRINTF("Start transfer ... | 145,576,340,832,680,440,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2021-3507 | A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). It could occur in fdctrl_transfer_handler() in hw/block/fdc.c while processing DMA read data transfers from the floppy drive to the guest system. A privileged guest user could use this flaw to crash the QEMU process on the hos... | https://nvd.nist.gov/vuln/detail/CVE-2021-3507 |
216,839 | qemu | 46609b90d9e3a6304def11038a76b58ff43f77bc | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/46609b90d9e3a6304def11038a76b58ff43f77bc | tests/qtest/fdc-test: Add a regression test for CVE-2021-3507
Add the reproducer from https://gitlab.com/qemu-project/qemu/-/issues/339
Without the previous commit, when running 'make check-qtest-i386'
with QEMU configured with '--enable-sanitizers' we get:
==4028352==ERROR: AddressSanitizer: heap-buffer-overflow ... | 1 | int main(int argc, char **argv)
{
int fd;
int ret;
/* Create a temporary raw image */
fd = mkstemp(test_image);
g_assert(fd >= 0);
ret = ftruncate(fd, TEST_IMAGE_SIZE);
g_assert(ret == 0);
close(fd);
/* Run the tests */
g_test_init(&argc, &argv, NULL);
qtest_start("-machin... | 145,371,748,963,576,930,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2021-3507 | A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). It could occur in fdctrl_transfer_handler() in hw/block/fdc.c while processing DMA read data transfers from the floppy drive to the guest system. A privileged guest user could use this flaw to crash the QEMU process on the hos... | https://nvd.nist.gov/vuln/detail/CVE-2021-3507 |
507,404 | qemu | 46609b90d9e3a6304def11038a76b58ff43f77bc | https://github.com/bonzini/qemu | https://gitlab.com/qemu-project/qemu/-/commit/46609b90d9e3a6304def11038a76b58ff43f77bc | tests/qtest/fdc-test: Add a regression test for CVE-2021-3507
Add the reproducer from https://gitlab.com/qemu-project/qemu/-/issues/339
Without the previous commit, when running 'make check-qtest-i386'
with QEMU configured with '--enable-sanitizers' we get:
==4028352==ERROR: AddressSanitizer: heap-buffer-overflow ... | 0 | int main(int argc, char **argv)
{
int fd;
int ret;
/* Create a temporary raw image */
fd = mkstemp(test_image);
g_assert(fd >= 0);
ret = ftruncate(fd, TEST_IMAGE_SIZE);
g_assert(ret == 0);
close(fd);
/* Run the tests */
g_test_init(&argc, &argv, NULL);
qtest_start("-machin... | 33,457,069,398,973,624,000,000,000,000,000,000,000 | None | null | [
"CWE-787"
] | CVE-2021-3507 | A heap buffer overflow was found in the floppy disk emulator of QEMU up to 6.0.0 (including). It could occur in fdctrl_transfer_handler() in hw/block/fdc.c while processing DMA read data transfers from the floppy drive to the guest system. A privileged guest user could use this flaw to crash the QEMU process on the hos... | https://nvd.nist.gov/vuln/detail/CVE-2021-3507 |
216,840 | graphviz | 784411ca3655c80da0f6025ab20634b2a6ff696b | https://gitlab.com/graphviz/graphviz | https://gitlab.com/graphviz/graphviz/-/commit/784411ca3655c80da0f6025ab20634b2a6ff696b | fix: out-of-bounds write on invalid label
When the label for a node cannot be parsed (due to it being malformed), it falls
back on the symbol name of the node itself. I.e. the default label the node
would have had if it had no label attribute at all. However, this is applied by
dynamically altering the node's label to... | 1 | static void record_init(node_t * n)
{
field_t *info;
pointf ul, sz;
int flip, len;
char *textbuf; /* temp buffer for storing labels */
int sides = BOTTOM | RIGHT | TOP | LEFT;
/* Always use rankdir to determine how records are laid out */
flip = NOT(GD_realflip(agraphof(n)));
reclblp =... | 110,568,576,039,017,220,000,000,000,000,000,000,000 | None | null | [
"CWE-120"
] | CVE-2020-18032 | Buffer Overflow in Graphviz Graph Visualization Tools from commit ID f8b9e035 and earlier allows remote attackers to execute arbitrary code or cause a denial of service (application crash) by loading a crafted file into the "lib/common/shapes.c" component. | https://nvd.nist.gov/vuln/detail/CVE-2020-18032 |
507,442 | graphviz | 784411ca3655c80da0f6025ab20634b2a6ff696b | https://gitlab.com/graphviz/graphviz | https://gitlab.com/graphviz/graphviz/-/commit/784411ca3655c80da0f6025ab20634b2a6ff696b | fix: out-of-bounds write on invalid label
When the label for a node cannot be parsed (due to it being malformed), it falls
back on the symbol name of the node itself. I.e. the default label the node
would have had if it had no label attribute at all. However, this is applied by
dynamically altering the node's label to... | 0 | static void record_init(node_t * n)
{
field_t *info;
pointf ul, sz;
int flip, len;
char *textbuf; /* temp buffer for storing labels */
int sides = BOTTOM | RIGHT | TOP | LEFT;
/* Always use rankdir to determine how records are laid out */
flip = NOT(GD_realflip(agraphof(n)));
reclblp =... | 211,930,348,113,326,280,000,000,000,000,000,000,000 | None | null | [
"CWE-120"
] | CVE-2020-18032 | Buffer Overflow in Graphviz Graph Visualization Tools from commit ID f8b9e035 and earlier allows remote attackers to execute arbitrary code or cause a denial of service (application crash) by loading a crafted file into the "lib/common/shapes.c" component. | https://nvd.nist.gov/vuln/detail/CVE-2020-18032 |
216,857 | node | a3c33d4ce78f74d1cf1765704af5b427aa3840a6 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/a3c33d4ce78f74d1cf1765704af5b427aa3840a6 | http2: update handling of rst_stream with error code NGHTTP2_CANCEL
The PR updates the handling of rst_stream frames and adds all streams
to the pending list on receiving rst frames with the error code
NGHTTP2_CANCEL.
The changes will remove dependency on the stream state that may allow
bypassing the checks in certai... | 1 | void Http2Stream::SubmitRstStream(const uint32_t code) {
CHECK(!this->is_destroyed());
code_ = code;
// If RST_STREAM frame is received and stream is not writable
// because it is busy reading data, don't try force purging it.
// Instead add the stream to pending stream list and process
// the pending data... | 81,741,339,616,528,470,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2021-22940 | Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior. | https://nvd.nist.gov/vuln/detail/CVE-2021-22940 |
507,615 | node | a3c33d4ce78f74d1cf1765704af5b427aa3840a6 | https://github.com/joyent/node | https://github.com/nodejs/node/commit/a3c33d4ce78f74d1cf1765704af5b427aa3840a6 | http2: update handling of rst_stream with error code NGHTTP2_CANCEL
The PR updates the handling of rst_stream frames and adds all streams
to the pending list on receiving rst frames with the error code
NGHTTP2_CANCEL.
The changes will remove dependency on the stream state that may allow
bypassing the checks in certai... | 0 | void Http2Stream::SubmitRstStream(const uint32_t code) {
CHECK(!this->is_destroyed());
code_ = code;
auto is_stream_cancel = [](const uint32_t code) {
return code == NGHTTP2_CANCEL;
};
// If RST_STREAM frame is received with error code NGHTTP2_CANCEL,
// add it to the pending list and don't force purg... | 62,829,948,650,623,250,000,000,000,000,000,000,000 | None | null | [
"CWE-416"
] | CVE-2021-22940 | Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior. | https://nvd.nist.gov/vuln/detail/CVE-2021-22940 |
216,862 | openssl | 2d0e5d4a4a5d4332325b5e5cea492fad2be633e1 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/2d0e5d4a4a5d4332325b5e5cea492fad2be633e1 | Fix NETSCAPE_SPKI_print function to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | int NETSCAPE_SPKI_print(BIO *out, NETSCAPE_SPKI *spki)
{
EVP_PKEY *pkey;
ASN1_IA5STRING *chal;
ASN1_OBJECT *spkioid;
int i, n;
char *s;
BIO_printf(out, "Netscape SPKI:\n");
X509_PUBKEY_get0_param(&spkioid, NULL, NULL, NULL, spki->spkac->pubkey);
i = OBJ_obj2nid(spkioid);
BIO_printf(o... | 175,540,212,050,256,030,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
507,782 | openssl | 2d0e5d4a4a5d4332325b5e5cea492fad2be633e1 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/2d0e5d4a4a5d4332325b5e5cea492fad2be633e1 | Fix NETSCAPE_SPKI_print function to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | int NETSCAPE_SPKI_print(BIO *out, NETSCAPE_SPKI *spki)
{
EVP_PKEY *pkey;
ASN1_IA5STRING *chal;
ASN1_OBJECT *spkioid;
int i, n;
char *s;
BIO_printf(out, "Netscape SPKI:\n");
X509_PUBKEY_get0_param(&spkioid, NULL, NULL, NULL, spki->spkac->pubkey);
i = OBJ_obj2nid(spkioid);
BIO_printf(o... | 259,378,294,628,884,240,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
216,863 | openssl | bb4d2ed4091408404e18b3326e3df67848ef63d0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/bb4d2ed4091408404e18b3326e3df67848ef63d0 | Fix append_ia5 function to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | static int append_ia5(STACK_OF(OPENSSL_STRING) **sk, const ASN1_IA5STRING *email)
{
char *emtmp;
/* First some sanity checks */
if (email->type != V_ASN1_IA5STRING)
return 1;
if (!email->data || !email->length)
return 1;
if (*sk == NULL)
*sk = sk_OPENSSL_STRING_new(sk_strcmp)... | 100,198,903,064,881,430,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
507,808 | openssl | bb4d2ed4091408404e18b3326e3df67848ef63d0 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/bb4d2ed4091408404e18b3326e3df67848ef63d0 | Fix append_ia5 function to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | static int append_ia5(STACK_OF(OPENSSL_STRING) **sk, const ASN1_IA5STRING *email)
{
char *emtmp;
/* First some sanity checks */
if (email->type != V_ASN1_IA5STRING)
return 1;
if (email->data == NULL || email->length == 0)
return 1;
if (memchr(email->data, 0, email->length) != NULL)
... | 22,421,527,675,965,504,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
216,864 | openssl | 4de66925203ca99189c842136ec4a623137ea447 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/4de66925203ca99189c842136ec4a623137ea447 | Fix test code to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | static int test_x509_time(int idx)
{
ASN1_TIME *t = NULL;
int result, rv = 0;
if (x509_format_tests[idx].set_string) {
/* set-string mode */
t = ASN1_TIME_new();
if (t == NULL) {
TEST_info("test_x509_time(%d) failed: internal error\n", idx);
return 0;
... | 314,932,103,710,780,020,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
507,832 | openssl | 4de66925203ca99189c842136ec4a623137ea447 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/4de66925203ca99189c842136ec4a623137ea447 | Fix test code to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | static int test_x509_time(int idx)
{
ASN1_TIME *t = NULL;
int result, rv = 0;
if (x509_format_tests[idx].set_string) {
/* set-string mode */
t = ASN1_TIME_new();
if (t == NULL) {
TEST_info("test_x509_time(%d) failed: internal error\n", idx);
return 0;
... | 191,092,689,006,157,140,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
216,871 | openssl | 23446958685a593d4d9434475734b99138902ed2 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/23446958685a593d4d9434475734b99138902ed2 | Fix printing of PROXY_CERT_INFO_EXTENSION to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 1 | static int i2r_pci(X509V3_EXT_METHOD *method, PROXY_CERT_INFO_EXTENSION *pci,
BIO *out, int indent)
{
BIO_printf(out, "%*sPath Length Constraint: ", indent, "");
if (pci->pcPathLengthConstraint)
i2a_ASN1_INTEGER(out, pci->pcPathLengthConstraint);
else
BIO_printf(out, "infi... | 277,287,998,004,405,700,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
507,853 | openssl | 23446958685a593d4d9434475734b99138902ed2 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/23446958685a593d4d9434475734b99138902ed2 | Fix printing of PROXY_CERT_INFO_EXTENSION to not assume NUL terminated strings
ASN.1 strings may not be NUL terminated. Don't assume they are.
CVE-2021-3712
Reviewed-by: Viktor Dukhovni <viktor@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org> | 0 | static int i2r_pci(X509V3_EXT_METHOD *method, PROXY_CERT_INFO_EXTENSION *pci,
BIO *out, int indent)
{
BIO_printf(out, "%*sPath Length Constraint: ", indent, "");
if (pci->pcPathLengthConstraint)
i2a_ASN1_INTEGER(out, pci->pcPathLengthConstraint);
else
BIO_printf(out, "infi... | 291,842,418,864,040,780,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
216,874 | openssl | d9d838ddc0ed083fb4c26dd067e71aad7c65ad16 | https://github.com/openssl/openssl | https://github.com/openssl/openssl/commit/d9d838ddc0ed083fb4c26dd067e71aad7c65ad16 | Fix a read buffer overrun in X509_aux_print().
The ASN1_STRING_get0_data(3) manual explitely cautions the reader
that the data is not necessarily NUL-terminated, and the function
X509_alias_set1(3) does not sanitize the data passed into it in any
way either, so we must assume the return value from X509_alias_get0(3)
i... | 1 | int X509_aux_print(BIO *out, X509 *x, int indent)
{
char oidstr[80], first;
STACK_OF(ASN1_OBJECT) *trust, *reject;
const unsigned char *alias, *keyid;
int keyidlen;
int i;
if (X509_trusted(x) == 0)
return 1;
trust = X509_get0_trust_objects(x);
reject = X509_get0_reject_objects(x)... | 252,393,493,912,061,800,000,000,000,000,000,000,000 | None | null | [
"CWE-125"
] | CVE-2021-3712 | ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a str... | https://nvd.nist.gov/vuln/detail/CVE-2021-3712 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.