| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in beego up to 2.0.1. This vulnerability affects unknown code of the component Route Lookup Handler. The manipulation leads to access control. This vulnerability is traded as CVE-2021-30080. There is no exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in beego up to 2.0.1 and classified as critical. This issue affects an unknown code of the component Route Lookup Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability.
The weakness was shared 04/05/2022 as d5df5e470d0a8ed291930ae802fd7e6b95226519. The advisory is shared at github.com. The identification of this vulnerability is CVE-2021-30080 since 04/02/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying the patch d5df5e470d0a8ed291930ae802fd7e6b95226519 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/beego/beego/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.5
VulDB Temp Score: 5.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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: d5df5e470d0a8ed291930ae802fd7e6b95226519
Timeline
04/02/2021 🔍04/05/2022 🔍
04/05/2022 🔍
04/08/2022 🔍
Sources
Product: github.comAdvisory: d5df5e470d0a8ed291930ae802fd7e6b95226519
Status: Not defined
CVE: CVE-2021-30080 (🔍)
GCVE (CVE): GCVE-0-2021-30080
GCVE (VulDB): GCVE-100-196529
Entry
Created: 04/05/2022 21:47Updated: 04/08/2022 08:48
Changes: 04/05/2022 21:47 (40), 04/08/2022 08:48 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.