CVE-2023-0657

Low
3.4
0.05.010.0
Year
2024
Published
Nov 17, 2024
Known Affected Devices
0
CVSS Score
3.4

What is CVE-2023-0657?

A flaw was found in Keycloak. This issue occurs due to improperly enforcing token types when validating signatures locally. This could allow an authenticated attacker to exchange a logout token for an access token and possibly gain access to data outside of enforced permissions.

CVSS Vector Breakdown

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

Exploitable from an adjacent network (e.g. same LAN, Wi-Fi segment, Bluetooth).

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
Low

Basic user account required (e.g. standard login without admin rights).

UI
User Interaction
Required

Victim must take an action (e.g. click a link, open a file) for the exploit to succeed.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
Low

Some sensitive information is disclosed, but attacker has limited access.

I
Integrity Impact
Low

Attacker can modify some data, but scope or consequence is limited.

A
Availability Impact
None

No availability impact. Service remains fully operational.

Known Affected Devices

FAQ

How severe is CVE-2023-0657?

CVE-2023-0657 has a CVSS score of 3.4/10, rated as Low. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2023-0657?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2023-0657 scores 3.4/10 (Low). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2023-0657?

The list of devices confirmed to be affected by CVE-2023-0657 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2023-0657?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.