# CVE-2021-43129: Security feature bypass in n/a

> Attackers can bypass the Disable Right Click feature in Brightspace quizzes to copy or print content, undermining content protection measures.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m7pf-2qjx-4mqr

## What is CVE-2021-43129?

CVE-2021-43129 is a medium-severity vulnerability in n/a, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A bypass exists for Desire2Learn/D2L Brightspace’s “Disable Right Click” option in the quizzing feature, which allows a quiz-taker to access print and copy functionality via the browser’s right click menu even when “Disable Right Click” is enabled on the quiz.

## Which versions are affected by CVE-2021-43129?

It affects 1 product.


Products: D2l Brightspace.

## How do I fix CVE-2021-43129?

No fix has been published for CVE-2021-43129 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-43129 being exploited?

There is no known exploitation of CVE-2021-43129 in the wild and no public exploit code.

Public exploit code:

- Vulnerability in D2L Brightspace's Learning Management System(LMS) (github_poc): https://github.com/Skotizo/CVE-2021-43129

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43129 and fix it if it is affected.

What it is: CVE-2021-43129 is a medium-severity vulnerability in n/a, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43129 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-43129/ (Markdown: https://insights.sbomify.com/CVE-2021-43129/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-43129
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-43129
- OSV: https://osv.dev/vulnerability/CVE-2021-43129

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-43129/
Summaries are generated and may contain mistakes; the official description above is the record.