In mutt and neomutt the In-Reply-To email header field is not protected by cryptographic signing which allows an attacker to reuse an unencrypted but signed email message to impersonate the original sender.

CVE Database V5

Detailed information about CVE-2024-49394: Improper Verification of Cryptographic Signature. Get real-time updates, technical details, and mitigation strategies

CVE-2024-49394: Improper Verification of Cryptographic Signature - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2024-49394: Improper Verification of Cryptographic Signature

CVE-2024-1726 is a medium severity vulnerability in the RESTEasy Reactive implementation within Quarkus, where security checks on certain JAX-RS endpoints occur after serialization. This flaw allows attackers who know POST, PUT, or PATCH request paths to trigger excessive resource consumption, potentially causing denial of service. The vulnerability affects versions 0 through 3. 3. 0. CR1 and 3. 8. 0. CR1 of Quarkus. Exploitation does not require authentication or user interaction and can be performed remotely over the network.

CVE-2024-1726 identifies a vulnerability in the RESTEasy Reactive framework used by Quarkus, a popular Java framework for building microservices. The core issue arises because security checks for some JAX-RS endpoints are performed after the serialization process of HTTP requests. Serialization is resource-intensive, and performing it before security validation allows attackers to exploit this sequence by sending crafted POST, PUT, or PATCH requests to known endpoint paths. This results in excessive consumption of processing resources on the server, potentially leading to denial of service (DoS) conditions. The vulnerability affects multiple versions of Quarkus, including early releases and certain milestone versions (0, 3.3.0.CR1, 3.8.0.CR1). The CVSS v3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts availability without affecting confidentiality or integrity. Although no active exploits have been reported, the flaw could be leveraged by attackers to degrade service availability, especially in environments exposing these endpoints publicly. The vulnerability is particularly relevant for applications relying on RESTEasy Reactive for handling RESTful APIs, common in cloud-native and microservice architectures.

Detailed information about CVE-2024-1726: Improper Preservation of Permissions. Get real-time updates, technical details, and mitigation strategies.

CVE-2024-1726: Improper Preservation of Permissions - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2024-1726: Improper Preservation of Permissions

CVE-2024-1722 is a vulnerability in Keycloak version 4. 15. 0 where an overly restrictive account lockout mechanism can be exploited by a remote unauthenticated attacker to block other users from logging in. This flaw does not allow data theft or system compromise but can cause denial of service by locking accounts. The vulnerability has a low CVSS score of 3. 7, indicating limited impact and a higher attack complexity. No known exploits are currently in the wild, and no authentication or user interaction is required to trigger the lockout. European organizations using affected Keycloak versions for identity and access management may experience service disruption. Mitigation involves updating Keycloak to a fixed version once available or implementing compensating controls such as rate limiting and monitoring login attempts. Countries with significant Keycloak adoption in critical sectors, such as Germany, France, and the UK, are more likely to be affected.

CVE-2024-1722 identifies a vulnerability in Keycloak version 4.15.0 related to its account lockout mechanism. Keycloak is an open-source identity and access management solution widely used for single sign-on and authentication services. The flaw arises because the lockout mechanism is overly restrictive, allowing a remote unauthenticated attacker to trigger account lockouts for other users. This can be exploited by repeatedly attempting failed logins against target accounts, causing them to become locked and preventing legitimate users from accessing their accounts. The vulnerability does not allow attackers to gain unauthorized access or extract sensitive information, but it can cause denial of service by disrupting user authentication. The CVSS score of 3.7 reflects a low severity, primarily due to the lack of confidentiality or integrity impact, the requirement for high attack complexity, and no privileges or user interaction needed. No known exploits have been reported in the wild, and no patches or fixes are currently linked, indicating the need for vigilance and proactive mitigation. The vulnerability affects only version 4.15.0 of Keycloak, so organizations running other versions may not be impacted. The flaw highlights the risk of account lockout policies that are too aggressive, which can be weaponized for denial of service against authentication services.

Detailed information about CVE-2024-1722: Overly Restrictive Account Lockout Mechanism. Get real-time updates, technical details, and mitigation strategies.

CVE-2024-1722: Overly Restrictive Account Lockout Mechanism - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2024-1722: Overly Restrictive Account Lockout Mechanism

CVE-2023-4535 is an out-of-bounds read vulnerability in the OpenSC package's MyEID driver on Red Hat Enterprise Linux 9. It requires physical access and a specially crafted USB device or smart card to exploit. The flaw allows manipulation of APDU responses, potentially leading to unauthorized access to sensitive data. The vulnerability impacts confidentiality, integrity, and availability but has a medium severity score of 4. 5. No known exploits are currently in the wild. European organizations using Red Hat Enterprise Linux 9 with OpenSC and smart card authentication are at risk, especially in sectors requiring strong hardware-based security. Mitigations include applying vendor patches when available, restricting physical access, and monitoring for unusual device interactions. Countries with significant Red Hat Enterprise Linux adoption and critical infrastructure using smart cards, such as Germany, France, and the UK, are most likely affected.

CVE-2023-4535 is a medium severity out-of-bounds read vulnerability identified in the OpenSC package within the MyEID driver on Red Hat Enterprise Linux 9. The vulnerability arises when handling symmetric key encryption operations involving APDU (Application Protocol Data Unit) responses, which are used in communication with smart cards and USB security tokens. An attacker with physical access can exploit this flaw by connecting a specially crafted USB device or smart card that triggers the out-of-bounds read condition. This manipulation can lead to unauthorized disclosure or manipulation of sensitive cryptographic data, potentially compromising system security. The vulnerability requires high attack complexity, no privileges, and user interaction (physical device insertion), with a scope that affects confidentiality, integrity, and availability. Currently, there are no known exploits in the wild, and no patches have been explicitly linked in the provided data, though vendor updates are expected. The vulnerability is particularly relevant for environments relying on hardware-based authentication or encryption tokens, such as government, finance, and critical infrastructure sectors.

Detailed information about CVE-2023-4535: Out-of-bounds Read in Red Hat Red Hat Enterprise Linux 9 affecting Red Hat Red Hat Enterprise Linux 9. Get real-time u

CVE-2023-4535: Out-of-bounds Read in Red Hat Red Hat Enterprise Linux 9 - Live Threat Intelligence - Threat Radar | OffSeq.com

CVE-2023-4535: Out-of-bounds Read in Red Hat Red Hat Enterprise Linux 9

In mutt and neomutt, PGP encryption does not use the --hidden-recipient mode which may leak the Bcc email header field by inferring from the recipients info.

Detailed information about CVE-2024-49395: Exposure of Sensitive Information Through Metadata. Get real-time updates, technical details, and mitigation strategi

CVE-2024-49395: Exposure of Sensitive Information Through Metadata

CVE-2024-49395: Exposure of Sensitive Information Through Metadata

Description

Technical Details

Community Reviews

Related Threats

CVE-2024-49394: Improper Verification of Cryptographic Signature

CVE-2024-1726: Improper Preservation of Permissions

CVE-2024-1722: Overly Restrictive Account Lockout Mechanism

CVE-2023-4535: Out-of-bounds Read in Red Hat Red Hat Enterprise Linux 9

Salesforce Flags Unauthorized Data Access via Gainsight-Linked OAuth Activity

Actions

External Links

Need enhanced features?

Latest Threats

Keyboard Shortcuts

Navigation

Search & Filters

UI Controls

Accessibility