Insufficient Granularity of Access Control Affecting opendaylight package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.17% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-OPENDAYLIGHT-9893486
  • published29 Apr 2025
  • disclosed3 May 2022

Introduced: 3 May 2022

CVE-2022-0866  (opens in a new tab)
CWE-1220  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 opendaylight.

NVD Description

Note: Versions mentioned in the description apply only to the upstream opendaylight package and not the opendaylight package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is configured with a RunAs principal. In particular, the org.jboss.as.ejb3.component.EJBComponent class has an incomingRunAsIdentity field. This field is used by the org.jboss.as.ejb3.security.RunAsPrincipalInterceptor to keep track of the current identity prior to switching to a new identity created using the RunAs principal. The exploit consist that the EJBComponent#incomingRunAsIdentity field is currently just a SecurityIdentity. This means in a concurrent environment, where multiple users are repeatedly invoking an EJB that is configured with a RunAs principal, it's possible for the wrong the caller principal to be returned from EJBComponent#getCallerPrincipal. Similarly, it's also possible for EJBComponent#isCallerInRole to return the wrong value. Both of these methods rely on incomingRunAsIdentity. Affects all versions of JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.

CVSS Base Scores

version 3.1