D2L Learning Management System 20.21.7 Quizzing protection mechanism
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in D2L Learning Management System 20.21.7. The impacted element is an unknown function of the component Quizzing. This manipulation causes protection mechanism. This vulnerability is tracked as CVE-2021-43129. The attack is possible to be carried out remotely. No exploit exists. The suggested workaround should be applied.
Details
A vulnerability classified as critical was found in D2L Learning Management System 20.21.7 (Learning Management Software). Affected by this vulnerability is an unknown code of the component Quizzing. The manipulation with an unknown input leads to a protection mechanism vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 04/19/2022. The advisory is shared at github.com. This vulnerability is known as CVE-2021-43129 since 11/01/2021. Neither technical details nor an exploit are publicly available.
The best possible mitigation is suggested to be Workaround.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
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: Protection mechanismCWE: CWE-693
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: WorkaroundStatus: 🔍
0-Day Time: 🔍
Workaround: community.brightspace.com
Timeline
11/01/2021 🔍04/19/2022 🔍
04/19/2022 🔍
04/21/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2021-43129 (🔍)
GCVE (CVE): GCVE-0-2021-43129
GCVE (VulDB): GCVE-100-197677
Entry
Created: 04/19/2022 17:46Updated: 04/21/2022 20:33
Changes: 04/19/2022 17:46 (38), 04/21/2022 17:50 (1), 04/21/2022 20:33 (4)
Complete: 🔍
Committer: plloyd
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.