VulnerabilityPublished 6 Nov 2023Updated 20 Nov 2025

CVE-2023-4910: Red Hat 3scale API Management Platform 2 · Resource Exposure

Affects Red Hat 3scale API Management Platform 2Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2023-4910, European organizations should implement the following specific measures: 1) Configure the 3Scale Admin Portal and associated web servers to include HTTP headers that prevent caching of sensitive pages, such as 'Cache-Control: no-store, no-cache, must-revalidate' and 'Pragma: no-cache'. 2) Ensure that logout processes explicitly invalidate sessions and tokens server-side and redirect users to a non-sensitive page rather than allowing cached content to be displayed. 3) Educate users to close browser windows or clear cache after logout, especially on shared or public devices. 4) Employ browser security policies or extensions that enforce strict cache control for sensitive applications. 5) Monitor API token usage for anomalies that might indicate token leakage or misuse. 6) Keep the Red Hat 3scale platform updated with the latest security patches once available. 7) Consider implementing multi-factor authentication (MFA) for API access to reduce the impact of token exposure. These steps go beyond generic advice by focusing on cache control headers, logout flow improvements, and user behavior to specifically address the root cause of the vulnerability.

Description

A flaw was found In 3Scale Admin Portal. If a user logs out from the personal tokens page and then presses the back button in the browser, the tokens page is rendered from the browser cache.

Impact

For European organizations, the primary impact of CVE-2023-4910 is the potential unauthorized disclosure of API personal tokens, which can lead to unauthorized API access and data leakage. This compromises confidentiality but does not affect data integrity or system availability. Organizations relying on Red Hat 3scale for managing APIs, especially those handling sensitive or regulated data, face increased risk of credential exposure if users share or lose control of their devices. This is particularly critical in sectors such as finance, healthcare, and government, where API security is paramount. The vulnerability could facilitate lateral movement or unauthorized API calls if tokens are accessed by malicious actors. However, exploitation requires local access to the user's browser session, limiting remote attack feasibility. The lack of known exploits reduces immediate risk but does not eliminate the need for remediation. Failure to address this issue could lead to compliance violations under GDPR or other data protection regulations if personal or sensitive data is exposed through compromised APIs.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 20 Nov 2025, 19:04 UTC

Technical details

References

Community reviews

Related threats