Security readout for executives and security teams
Plain-English summary
Claroty Secure Access versions 3.3.0 through 4.0.2 may mishandle OIDC sign-in, allowing an unauthenticated remote attacker to create unauthorized users or impersonate existing users. Successful abuse could compromise sensitive access and operations. The high attack complexity reduces likelihood but does not offset the potentially severe impact.
Executive priority
Treat affected OIDC-enabled deployments as an urgent identity-security issue. Promptly identify exposed systems, obtain Claroty’s prescribed remediation, and examine authentication records for compromise. Prioritize systems providing access to sensitive or operational environments. Absence from KEV lowers confidence of widespread exploitation, but it does not reduce the potential consequence of successful impersonation.
Technical view
The flaw is an incorrect OIDC authentication flow classified as CWE-284. It is remotely reachable, requires no privileges or user interaction, and has high attack complexity. The CVSS 3.1 vector indicates scope change and potentially high confidentiality, integrity, and availability impact. The supplied sources do not describe the exact prerequisite configuration or remediation release.
Likely exposure
Exposure is most likely where Claroty Secure Access 3.3.0–4.0.2 uses OIDC authentication and its authentication interface is reachable by an attacker. The source bundle does not establish whether every OIDC configuration is vulnerable, so organizations should validate their exact deployment against Claroty’s advisory.
Exploitation context
The supplied record does not report active exploitation, and the CVE is not identified as a KEV entry. Exploitation requires high complexity, but no authentication or victim interaction. Evidence supports unauthorized account creation or OIDC-user impersonation; it does not establish a public exploit or observed attacks.
Researcher notes
The public description establishes an authentication-flow authorization failure but provides no protocol-level mechanics, configuration prerequisites, indicators of compromise, or confirmed fixed version in the supplied material. CVSS 9.0 reflects remote, unauthenticated attack potential with high complexity and scope change. Testing should remain defensive and authorized, emphasizing version, OIDC configuration, account provenance, and session identity mapping.
Mitigation direction
- Consult Claroty’s advisory for the approved fixed release or configuration changes.
- Contact Claroty support if the advisory does not clearly cover the deployed OIDC configuration.
- Restrict Secure Access authentication interfaces to trusted networks while remediation is pending.
- Review and disable unauthorized accounts without disrupting legitimate operational access.
Validation and detection
- Inventory Claroty Secure Access versions and identify deployments running 3.3.0 through 4.0.2.
- Confirm which deployments use OIDC and document their identity-provider configuration.
- Review user-creation and authentication records for unexpected accounts or identity mismatches.
- Verify vendor-directed remediation and retest legitimate OIDC authentication afterward.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-54603 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H2.26CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9CriticalVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://claroty.com/CVE reference, mitre
- https://claroty.com/product-security/oidc-configurations-in-claroty-secure-accessCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.