In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() er
Detection of Error Condition Without Action vulnerability in Apache Tomcat when configuring CRLs for a FFM based connect
Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. From 0.4.0 to before 0
A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; durin
pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.1, src/evdev.c silently
Improper handling of error condition during host-induced faults can allow a local high-privileged attack to selectively
Frequently Asked Questions
What is CWE-390?
CWE-390 (CWE-390) 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-390?
There are 7 CVE records associated with CWE-390 in our database. Of these, 2 are critical severity, 0 are high severity, and 3 are medium severity.
How can I protect against CWE-390 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-390 using AI-powered security agents.
Detect CWE-390 Vulnerabilities
CyberStrike's AI agents automatically detect cwe-390 vulnerabilities across your infrastructure.
Get Started