| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in IRISNext up to 9.8.28. Affected by this issue is some unknown functionality of the component BeanShell. Performing a manipulation results in an unknown weakness. This vulnerability is reported as CVE-2022-26111. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, was found in IRISNext up to 9.8.28. This affects an unknown functionality of the component BeanShell. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 04/26/2022. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-26111 since 02/25/2022. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 9.8.0
- 9.8.1
- 9.8.2
- 9.8.3
- 9.8.4
- 9.8.5
- 9.8.6
- 9.8.7
- 9.8.8
- 9.8.9
- 9.8.10
- 9.8.11
- 9.8.12
- 9.8.13
- 9.8.14
- 9.8.15
- 9.8.16
- 9.8.17
- 9.8.18
- 9.8.19
- 9.8.20
- 9.8.21
- 9.8.22
- 9.8.23
- 9.8.24
- 9.8.25
- 9.8.26
- 9.8.27
- 9.8.28
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/25/2022 🔍04/26/2022 🔍
04/26/2022 🔍
04/29/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-26111 (🔍)
GCVE (CVE): GCVE-0-2022-26111
GCVE (VulDB): GCVE-100-198507
Entry
Created: 04/26/2022 10:18Updated: 04/29/2022 15:36
Changes: 04/26/2022 10:18 (34), 04/29/2022 15:36 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.