# CVE-2023-43091: Gnome-maps: gnome maps is vulnerable to a code injection attack (similar to xss) via its service.json

> An attacker can execute arbitrary code by providing a malicious service.json configuration file to GNOME Maps.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** DEBIAN-CVE-2023-43091, GHSA-8jrf-4f89-74jx, UBUNTU-CVE-2023-43091

## What is CVE-2023-43091?

CVE-2023-43091 is a critical code injection vulnerability in gnome:gnome-maps, published on 17 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in GNOME Maps, which is vulnerable to a code injection attack via its service.json configuration file. If the configuration file is malicious, it may execute arbitrary code.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Gnome Gnome-Maps.

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

Apply the vendor's patch.

## Is CVE-2023-43091 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43091 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43091 is a critical code injection vulnerability in gnome:gnome-maps, published on 17 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43091 exists.

Affected product: gnome:gnome-maps. 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-43091/ (Markdown: https://insights.sbomify.com/CVE-2023-43091/index.md)
```

## Sources

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

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