huzaifas-sidhpurwala/security-commit huggingface dataset:
CVE-2016-0758: kernel: tags with indefinite length can corrupt pointers in asn1_find_indefinite_length()
Component: kernel
Severity: Important
CWE: CWE-120 (Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'))
Public date: 2016-05-12T00:00:00+00:00

A flaw was found in the way the Linux kernel's ASN.1 DER decoder processed certain certificate files with tags of indefinite length. A local, unprivileged user could use a specially crafted X.509 certificate DER file to crash the system or, potentially, escalate their privileges on the system.

Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 and 6.

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 7 and Red Hat Enterprise MRG 2.

Affected upstream versions: n/a
Fixed upstream versions: v4.6
Upstream repository: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Upstream fix commit: 23c8a812dc3c621009e4f0e5342aa4e2ede1ceaa
CVE-2016-0772: python: smtplib StartTLS stripping attack
Component: python
Severity: Moderate
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-06-11T00:00:00+00:00

It was found that Python's smtplib library did not return an exception when StartTLS failed to be established in the SMTP.starttls() function. A man in the middle attacker could strip out the STARTTLS command without generating an exception on the Python SMTP client application, preventing the establishment of the TLS layer.


Affected upstream versions: n/a
Upstream repository: https://hg.python.org/cpython
Upstream fix commit: d590114c2394
CVE-2016-0797: OpenSSL: BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
Component: OpenSSL
Severity: Low
Public date: 2016-03-01T00:00:00+00:00

An integer overflow flaw, leading to a NULL pointer dereference or a heap-based memory corruption, was found in the way some BIGNUM functions of OpenSSL were implemented. Applications that use these functions with large untrusted input could crash or, potentially, execute arbitrary code.


Affected upstream versions: n/a
Fixed upstream versions: OpenSSL_1_0_2g
Upstream repository: https://git.openssl.org/openssl.git
Upstream fix commit: c175308407858afff3fc8c2e5e085d94d12edc7d
CVE-2016-0799: OpenSSL: Fix memory issues in BIO_*printf functions
Component: OpenSSL
Severity: Low
Public date: 2016-02-26T00:00:00+00:00

Several flaws were found in the way BIO_*printf functions were implemented in OpenSSL. Applications which passed large amounts of untrusted data through these functions could crash or potentially execute code with the permissions of the user running such an application.

Statement: The original issue fixed by OpenSSL upstream contains two distinct fixes. The first one is a format string flaw in the internal fmtstr functions, which may result in a OOB read flaw when printing very large string. This issue was assigned CVE-2016-0799

The second issue relates to the internal doapr_outch function of OpenSSL. It can result in an OOB write, or cause memory leaks. This issue has been assigned CVE-2016-2842 by MITRE as is now tracked as https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-2842

Affected upstream versions: n/a
Fixed upstream versions: OpenSSL_1_0_2g
Upstream repository: https://git.openssl.org/openssl.git
Upstream fix commit: 578b956fe741bf8e84055547b1e83c28dd902c73
CVE-2016-1000232: nodejs-tough-cookie: regular expression DoS via Cookie header with many semicolons
Component: nodejs-tough-cookie
Severity: Moderate
CWE: CWE-400 (Uncontrolled Resource Consumption)
CVSS v3: 5.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
Public date: 2016-07-22T00:00:00+00:00

A regular expression denial of service flaw was found in Tough-Cookie. An attacker able to make an application using Touch-Cookie to parse an HTTP header with many semicolons could cause the application to consume an excessive amount of CPU.


Affected upstream versions: n/a
Fixed upstream versions: v2.3.0
Upstream repository: https://github.com/salesforce/tough-cookie
Upstream fix commit: 615627206357d997d5e6ff9da158997de05235ae
CVE-2016-1000338: bouncycastle: DSA does not fully validate ASN.1 encoding during signature verification allowing for injection of unsigned data
Component: bouncycastle
Severity: Moderate
CWE: CWE-325 (Missing Cryptographic Step)
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-10-15T00:00:00+00:00

In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: b0c3ce99d43d73a096268831d0d120ffc89eac7f
CVE-2016-1000339: bouncycastle: Information leak in AESFastEngine class
Component: bouncycastle
Severity: Moderate
CWE: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)
CVSS v3: 5.1 (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
Public date: 2018-06-07T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 8a73f08931450c17c749af067b6a8185abdfd2c0
CVE-2016-1000340: bouncycastle: Carry propagation bug in math.raw.Nat??? class
Component: bouncycastle
Severity: Low
CWE: CWE-682 (Incorrect Calculation)
CVSS v3: 2.9 (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)
Public date: 2018-06-07T00:00:00+00:00

In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Low. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 790642084c4e0cadd47352054f868cc8397e2c00
CVE-2016-1000341: bouncycastle: Information exposure in DSA signature generation via timing attack
Component: bouncycastle
Severity: Moderate
CWE: CWE-385 (Covert Timing Channel)
CVSS v3: 5.1 (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
Public date: 2018-06-07T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Where timings can be closely observed for the generation of signatures, the lack of blinding in 1.55, or earlier, may allow an attacker to gain information about the signature's k value and ultimately the private value as well.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: acaac81f96fec91ab45bd0412beaf9c3acd8defa
CVE-2016-1000342: bouncycastle: ECDSA improper validation of ASN.1 encoding of signature
Component: bouncycastle
Severity: Moderate
CWE: CWE-295 (Improper Certificate Validation)
CVSS v3: 5.1 (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N)
Public date: 2018-06-07T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 843c2e60f67d71faf81d236f448ebbe56c62c647
CVE-2016-1000343: bouncycastle: DSA key pair generator generates a weak private key by default
Component: bouncycastle
Severity: Low
CWE: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))
CVSS v3: 2.9 (CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)
Public date: 2018-06-07T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Low. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 50a53068c094d6cff37659da33c9b4505becd389
CVE-2016-1000344: bouncycastle: DHIES implementation allowed the use of ECB mode
Component: bouncycastle
Severity: Moderate
CWE: CWE-325 (Missing Cryptographic Step)
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-04-27T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 9385b0ebd277724b167fe1d1456e3c112112be1f
CVE-2016-1000345: bouncycastle: DHIES/ECIES CBC modes are vulnerable to padding oracle attack
Component: bouncycastle
Severity: Moderate
CWE: CWE-325 (Missing Cryptographic Step)
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-04-27T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35
CVE-2016-1000346: bouncycastle: Other party DH public keys are not fully validated
Component: bouncycastle
Severity: Moderate
CWE: CWE-325 (Missing Cryptographic Step)
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-10-29T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 1127131c89021612c6eefa26dbe5714c194e7495
CVE-2016-1000352: bouncycastle: ECIES implementation allowed the use of ECB mode
Component: bouncycastle
Severity: Moderate
CWE: CWE-325 (Missing Cryptographic Step)
CVSS v3: 4.8 (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-04-27T00:00:00+00:00

In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

Statement: This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: r1rv56
Upstream repository: https://github.com/bcgit/bc-java
Upstream fix commit: 9385b0ebd277724b167fe1d1456e3c112112be1f
CVE-2016-10009: openssh: loading of untrusted PKCS#11 modules in ssh-agent
Component: openssh
Severity: Moderate
CVSS v3: 6.6 (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H)
Public date: 2016-12-19T00:00:00+00:00

It was found that ssh-agent could load PKCS#11 modules from arbitrary paths. An attacker having control of the forwarded agent-socket on the server, and the ability to write to the filesystem of the client host, could use this flaw to execute arbitrary code with the privileges of the user running ssh-agent.

Statement: In order to exploit this flaw, the attacker needs to have control of the forwarded agent-socket and the ability to write to the filesystem of the host running ssh-agent. Because of this restriction for successful exploitation, this issue has been rated as having Moderate security impact. A future update may address this flaw.

Affected upstream versions: n/a
Upstream repository: https://github.com/openbsd/src
Upstream fix commit: 9476ce1dd37d3c3218d5640b74c34c65e5f4efe5
CVE-2016-10011: openssh: Leak of host private key material to privilege-separated child process via realloc()
Component: openssh
Severity: Low
CWE: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)
CVSS v3: 2.5 (CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N)
Public date: 2016-12-19T00:00:00+00:00

It was found that the host private key material could possibly leak to the privilege-separated child processes via re-allocated memory. An attacker able to compromise the privilege-separated process could therefore obtain the leaked key information.

Statement: It seems that this flaw is not practically exploitable, the leak of host private key material to the privilege-separated child processes is theoretical. No such leak was observed in practice for normal-sized keys, nor does a leak to the child processes directly expose key material to unprivileged users. Because of the this restriction for successful exploitation, this issue has been rated as having Low security impact. A future update may address this flaw.

Affected upstream versions: n/a
Upstream repository: https://github.com/openbsd/src
Upstream fix commit: ac8147a06ed2e2403fb6b9a0c03e618a9333c0e9
CVE-2016-10012: openssh: Bounds check can be evaded in the shared memory manager used by pre-authentication compression support
Component: openssh
Severity: Low
CWE: CWE-287 (Improper Authentication)
CVSS v3: 4.2 (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)
Public date: 2016-12-19T00:00:00+00:00

It was found that the boundary checks in the code implementing support for pre-authentication compression could have been optimized out by certain compilers. An attacker able to compromise the privilege-separated process could possibly use this flaw for further attacks against the privileged monitor process.

Statement: In order to exploit this flaw, the attacker needs to first compromise the sandboxed privilege-separation process by using another security flaw. Because of this restriction for successful exploitation, this issue has been rated as having Low security impact.

Affected upstream versions: n/a
Upstream repository: https://github.com/openbsd/src
Upstream fix commit: 3095060f479b86288e31c79ecbc5131a66bcd2f9
CVE-2016-10088: kernel: Use after free in SCSI generic device interface (CVE-2016-9576 regression)
Component: kernel
Severity: Moderate
CWE: CWE-416 (Use After Free)
CVSS v3: 7 (CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H)
Public date: 2017-01-11T00:00:00+00:00

It was found that the fix for CVE-2016-9576 was incomplete: the Linux kernel's sg implementation did not properly restrict write operations in situations where the KERNEL_DS option is set. A local attacker to read or write to arbitrary kernel memory locations or cause a denial of service (use-after-free) by leveraging write access to a /dev/sg device.

Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5 as the code which can trigger the flaw is not present in the products listed.

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6, 7 and MRG-2. Future Linux kernel updates for the respective releases might address this issue.

Affected upstream versions: n/a
Fixed upstream versions: v4.10
Upstream repository: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Upstream fix commit: 128394eff343fc6d2f32172f03e24829539c5835
CVE-2016-10147: kernel: Kernel crash by spawning mcrypt(alg) with incompatible algorithm
Component: kernel
Severity: Moderate
CWE: CWE-476 (NULL Pointer Dereference)
CVSS v3: 5.5 (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2016-12-02T00:00:00+00:00

Algorithms not compatible with mcryptd could be spawned by mcryptd with a direct crypto_alloc_tfm invocation using a "mcryptd(alg)" name construct.  This causes mcryptd to crash the kernel if an arbitrary "alg" is incompatible and not intended to be used with mcryptd.

Statement: This issue does not affect the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG-2 as the flaw is not present in the products listed.

Affected upstream versions: n/a
Fixed upstream versions: v4.9
Upstream repository: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Upstream fix commit: 48a992727d82cb7db076fa15d372178743b1f4cd
CVE-2016-10149: python-pysaml2: Entity expansion issue
Component: python-pysaml2
Severity: Moderate
CWE: CWE-776 (Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion'))
CVSS v3: 5.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
Public date: 2016-10-31T00:00:00+00:00

An XML entity expansion vulnerability was found in python-pysaml2. A remote attacker could send a crafted request which would cause denial of service through resource exhaustion.


Affected upstream versions: n/a
Fixed upstream versions: 4.4.0-1
Upstream repository: https://github.com/rohe/pysaml2
Upstream fix commit: 6e09a25d9b4b7aa7a506853210a9a14100b8bc9b
CVE-2016-10155: Qemu: watchdog: memory leakage in virtual hardware watchdog wdt_i6300esb
Component: Qemu
Severity: Low
CWE: CWE-772 (Missing Release of Resource after Effective Lifetime)
CVSS v3: 4.1 (CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L)
Public date: 2016-12-22T00:00:00+00:00

Memory leak in hw/watchdog/wdt_i6300esb.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (host memory consumption and QEMU process crash) via a large number of device unplug operations.


Affected upstream versions: n/a
Fixed upstream versions: v2.9.0
Upstream repository: https://git.qemu.org/qemu.git
Upstream fix commit: eb7a20a3616085d46aa6b4b4224e15587ec67e6e
CVE-2016-10158: php: Wrong calculation in exif_convert_any_to_int function
Component: php
Severity: Moderate
CWE: CWE-682 (Incorrect Calculation)
CVSS v3: 5.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
Public date: 2017-01-19T00:00:00+00:00

It was found that the exif_convert_any_to_int() function in PHP was vulnerable to floating point exceptions when parsing tags in image files. A remote attacker with the ability to upload a malicious image could crash PHP, causing a Denial of Service.

Statement: Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Affected upstream versions: n/a
Fixed upstream versions: php-5.6.30
Upstream repository: https://github.com/php/php-src
Upstream fix commit: 1cda0d7c2ffb62d8331c64e703131d9cabdc03ea