In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Wher
In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack.
python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time compar
A command execution flaw on the Trend Micro Threat Discovery Appliance 2.6.1062r1 exists with the timezone parameter in
The verify function in Encryption/Symmetric.php in Malcolm Fell jwt before 1.0.3 does not use a timing-safe function for
The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was greate
Frequently Asked Questions
What is CWE-361?
CWE-361 (CWE-361) is a weakness category in the Common Weakness Enumeration (CWE) system maintained by MITRE. It describes a class of software or hardware vulnerability that can lead to security issues.
How many CVEs are classified as CWE-361?
There are 7 CVE records associated with CWE-361 in our database. Of these, 2 are critical severity, 2 are high severity, and 2 are medium severity.
How can I protect against CWE-361 vulnerabilities?
Protection strategies depend on the specific weakness type. General measures include input validation, secure coding practices, regular security testing, and keeping software up to date. CyberStrike can help by automatically scanning your infrastructure for vulnerabilities related to CWE-361 using AI-powered security agents.
Detect CWE-361 Vulnerabilities
CyberStrike's AI agents automatically detect cwe-361 vulnerabilities across your infrastructure.
Get Started