# CVE-2022-22909: Code injection in n/a

> Attackers can execute arbitrary code by injecting payloads into the room name field in HotelDruid.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-22909, GHSA-mgcc-qmq4-wwgm, UBUNTU-CVE-2022-22909

## What is CVE-2022-22909?

CVE-2022-22909 is a high-severity code injection vulnerability in n/a, published on 2 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HotelDruid v3.0.3 was discovered to contain a remote code execution (RCE) vulnerability which is exploited via an attacker inserting a crafted payload into the name field under the Create New Room module.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2022-22909?

It affects 1 product.


Products: Digitaldruid Hoteldruid.

## How do I fix CVE-2022-22909?

Upgrade to a fixed version.

## Is CVE-2022-22909 being exploited?

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

Public exploit code:

- Hotel Druid 3.0.3 Code Injection to Remote Code Execution (github_poc): https://github.com/0z09e/CVE-2022-22909
-  Exploits for Hotel Druid 3.0.3 - Remote Code Execution (RCE)  CVE-2022-22909 (github_poc): https://github.com/kaal18/CVE-2022-22909
- Hotel Druid 3.0.3 - Remote Code Execution (RCE) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-43371](https://insights.sbomify.com/CVE-2023-43371/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43373](https://insights.sbomify.com/CVE-2023-43373/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43374](https://insights.sbomify.com/CVE-2023-43374/): SQL injection in n/a (critical 9.8)
- [CVE-2023-43375](https://insights.sbomify.com/CVE-2023-43375/): SQL injection in n/a (critical 9.8)
- [CVE-2021-42949](https://insights.sbomify.com/CVE-2021-42949/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22909 and fix it if it is affected.

What it is: CVE-2022-22909 is a high-severity code injection vulnerability in n/a, published on 2 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22909 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-2022-22909/ (Markdown: https://insights.sbomify.com/CVE-2022-22909/index.md)
```

## Sources

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

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