# CVE-2023-33244: Security feature bypass in n/a

> Attackers can bypass security restrictions to access microphone, camera, and notifications via embedded web pages in Obsidian.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 20 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-9w8g-4mjw-jw3p

## What is CVE-2023-33244?

CVE-2023-33244 is a high-severity vulnerability in n/a, published on 20 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Obsidian before 1.2.2 allows calls to unintended APIs (for microphone access, camera access, and desktop notification) via an embedded web page.

## Which versions are affected by CVE-2023-33244?

It affects 1 product.


Products: Obsidian Obsidian.

## How do I fix CVE-2023-33244?

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

## Is CVE-2023-33244 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38148](https://insights.sbomify.com/CVE-2021-38148/): Obsidian does not require user confirmation for non-http/https URLs. (critical 9.8)
- [CVE-2023-2110](https://insights.sbomify.com/CVE-2023-2110/): Obsidian Local File Disclosure (high 8.2)
- [CVE-2022-36450](https://insights.sbomify.com/CVE-2022-36450/): Code injection in n/a (high 8.0)
- [CVE-2023-27035](https://insights.sbomify.com/CVE-2023-27035/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33244 and fix it if it is affected.

What it is: CVE-2023-33244 is a high-severity vulnerability in n/a, published on 20 May 2023. 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-2023-33244 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-2023-33244/ (Markdown: https://insights.sbomify.com/CVE-2023-33244/index.md)
```

## Sources

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

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