Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2022-0866

Quick assessment

Affected
n/a Wildfly
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Wildfly是Wildfly的一款功能强大、模块化且轻量级的应用程序服务器。 WildFly 中存在安全漏洞,该漏洞源于当使用 Elytron Security 时,它会在某些高度并发的情况下返回错误的调用者主体。

AI Predicted 5.4 Difficulty: Moderate EPSS 0.87% · P56

Possible ATT&CK Techniques 1 AI

T1078 · Valid Accounts
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-0866

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
N/A
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5
Vulnerability Title
Wildfly 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Wildfly是Wildfly的一款功能强大、模块化且轻量级的应用程序服务器。 WildFly 中存在安全漏洞,该漏洞源于当使用 Elytron Security 时,它会在某些高度并发的情况下返回错误的调用者主体。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
- Wildfly JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled. -

II. Public POCs for CVE-2022-0866

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-0866

登录查看更多情报信息。

Vendor Advisories for CVE-2022-0866 (1)

Same Patch Batch · n/a · 2022-05-10 · 65 CVEs total

CVE-2022-28910 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-29328 D-Link DAP-1330 缓冲区错误漏洞
CVE-2022-29591 Tenda TX9 Pro 安全漏洞
CVE-2022-28110 Hotel Management System SQL注入漏洞
CVE-2022-29329 D-Link DAP-1330 缓冲区错误漏洞
CVE-2022-28905 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28908 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28907 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28909 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28911 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28906 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28913 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28912 TOTOLINK N600R 操作系统命令注入漏洞
CVE-2022-28901 D-Link DIR882 操作系统命令注入漏洞
CVE-2022-28895 D-Link DIR882 操作系统命令注入漏洞
CVE-2022-28896 D-Link DIR882 操作系统命令注入漏洞
CVE-2022-26987 多款产品缓冲区错误漏洞
CVE-2022-26988 多款产品缓冲区错误漏洞
CVE-2022-23676 Avaya switches缓冲区错误漏洞
CVE-2022-23677 Avaya switches 缓冲区错误漏洞

Showing top 20 of 65 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2022-0866

No comments yet


Leave a comment