What is the CVSS score of CVE-2024-45719?

CVE-2024-45719 has a CVSS 3.1 base score of 2.6 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2024-45719?

Yes, a patch is available for CVE-2024-45719. Update the affected software to the latest version immediately.

Answer CVE-2024-45719

LOW

Inadequate Encryption Strength (CWE-326)

2024-11-22 security@apache.org

Apache Information Disclosure Answer

2.6

CVSS 3.1 · Vendor: apache

Severity by source

Vendor (apache) PRIMARY

2.6 LOW

AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N

Primary rating from Vendor (apache) · only source for this CVE.

CVSS VectorVendor: apache

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Nov 22, 2024 - 15:15 cve.org

LOW 2.6

DescriptionCVE.org

Inadequate Encryption Strength vulnerability in Apache Answer.

This issue affects Apache Answer: through 1.4.0.

The ids generated using the UUID v1 version are to some extent not secure enough. It can cause the generated token to be predictable. Users are recommended to upgrade to version 1.4.1, which fixes the issue.

AnalysisAI

Inadequate Encryption Strength vulnerability in Apache Answer.4.0. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-326. Inadequate Encryption Strength vulnerability in Apache Answer.4.0. The ids generated using the UUID v1 version are to some extent not secure enough. It can cause the generated token to be predictable. Users are recommended to upgrade to version 1.4.1, which fixes the issue. Affected products include: Apache Answer. Version information: through 1.4.0..

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.