What is the CVSS score of CVE-2017-12973?

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

Is there a patch available for CVE-2017-12973?

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

Nimbus Jose Jwt CVE-2017-12973

LOW

Improper Validation of Integrity Check Value (CWE-354)

2017-08-20 cve@mitre.org

Information Disclosure Oracle Nimbus Jose Jwt

3.1

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

3.1 LOW

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Aug 20, 2017 - 16:29 cve.org

LOW 3.1

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

28 maven packages depend on com.nimbusds:nimbus-jose-jwt (3 direct, 25 indirect)

Ecosystem-wide dependent count for version 4.39.

DescriptionCVE.org

Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack.

AnalysisAI

Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack. Rated low severity (CVSS 3.1), this vulnerability is remotely exploitable, no authentication required.

Technical ContextAI

This vulnerability is classified under CWE-354. Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack. Affected products include: Connect2Id Nimbus Jose\+Jwt. Version information: before 4.39.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.