https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 17:07:13 +0000 https://cve.radiocsirt.org/vuln/certfr-2020-avi-420 certfr-2020-avi-420 https://cve.radiocsirt.org/vuln/certfr-2020-avi-420 https://cve.radiocsirt.org/vuln/cnvd-2018-11783 cnvd-2018-11783 https://cve.radiocsirt.org/vuln/cnvd-2018-11783 https://cve.radiocsirt.org/vuln/euvd-2026-88977 EUVD-2026-88977 https://cve.radiocsirt.org/vuln/euvd-2026-88977 https://cve.radiocsirt.org/vuln/fkie_cve-2016-1000339 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2016-1000339 https://cve.radiocsirt.org/vuln/ghsa-c8xf-m4ff-jcxj <p><strong>Affected:</strong> Maven: org.bouncycastle:bcprov-jdk14, Maven: org.bouncycastle:bcprov-jdk15, Maven: org.bouncycastle:bcprov-jdk15on</p> <p>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.</p> <p><strong>Affected:</strong> Maven: org.bouncycastle:bcprov-jdk14, Maven: org.bouncycastle:bcprov-jdk15, Maven: org.bouncycastle:bcprov-jdk15on</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-c8xf-m4ff-jcxj https://cve.radiocsirt.org/vuln/gsd-2016-1000339 gsd-2016-1000339 https://cve.radiocsirt.org/vuln/gsd-2016-1000339 https://cve.radiocsirt.org/vuln/opensuse-su-2024:10661-1 <p>bouncycastle-1.68-3.2 on GA media</p> <p>bouncycastle-1.68-3.2 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:10661-1 https://cve.radiocsirt.org/vuln/rhsa-2018:2669 <p>1: Class Loader manipulation via request parameters thrift: Improper file path sanitization in t_go_generator.cc:format_go_output() of the go client library can allow an attacker to inject commands bouncycastle: DSA does not fully validate ASN.1 encoding during signature verification allowing for injection of unsigned data bouncycastle: Information leak in AESFastEngine class bouncycastle: Carry propagation bug in math.raw.Nat??? class bouncycastle: Information exposure in DSA signature generation via timing attack bouncycastle: ECDSA improper validation of ASN.1 encoding of signature bouncycastle: DSA key pair generator generates a weak private key by default bouncycastle: DHIES implementation allowed the use of ECB mode bouncycastle: DHIES/ECIES CBC modes are vulnerable to padding oracle attack bouncycastle: Other party DH public keys are not fully validated bouncycastle: ECIES implementation allowed the use of ECB mode async-http-client: Invalid URL parsing with &#39;?&#39; undertow: File descriptor leak caused by JarURLConnection.getLastModified() allows attacker to cause a denial of service spring-framework: Directory traversal vulnerability with static resources on Windows filesystems spring-framework: Multipart content pollution tika: Infinite loop in BPGParser can allow remote attacker to cause a denial of service tika: Infinite loop in ChmParser can allow remote attacker to cause a denial of service pdfbox: Infinite loop in AFMParser.java allows for out of memory erros via…</p> <p>1: Class Loader manipulation via request parameters thrift: Improper file path sanitization in t_go_generator.cc:format_go_output() of the go client library can allow an attacker to inject commands bouncycastle: DSA does not fully validate ASN.1 encoding during signature verification allowing for injection of unsigned data bouncycastle: Information leak in AESFastEngine class bouncycastle: Carry propagation bug in math.raw.Nat??? class bouncycastle: Information exposure in DSA signature generation via timing attack bouncycastle: ECDSA improper validation of ASN.1 encoding of signature bouncycastle: DSA key pair generator generates a weak private key by default bouncycastle: DHIES implementation allowed the use of ECB mode bouncycastle: DHIES/ECIES CBC modes are vulnerable to padding oracle attack bouncycastle: Other party DH public keys are not fully validated bouncycastle: ECIES implementation allowed the use of ECB mode async-http-client: Invalid URL parsing with &#39;?&#39; undertow: File descriptor leak caused by JarURLConnection.getLastModified() allows attacker to cause a denial of service spring-framework: Directory traversal vulnerability with static resources on Windows filesystems spring-framework: Multipart content pollution tika: Infinite loop in BPGParser can allow remote attacker to cause a denial of service tika: Infinite loop in ChmParser can allow remote attacker to cause a denial of service pdfbox: Infinite loop in AFMParser.java allows for out of memory erros via…</p> https://cve.radiocsirt.org/vuln/rhsa-2018:2669 https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-1000339 <p><strong>Affected:</strong> Ubuntu:14.04:LTS: bouncycastle, Ubuntu:Pro:16.04:LTS: bouncycastle</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:14.04:LTS: bouncycastle, Ubuntu:Pro:16.04:LTS: bouncycastle</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2016-1000339