CVE-2023-43091

What it actually does

The vulnerability permits arbitrary command execution by processing attacker-controlled content within a service.json file, allowing injection of commands during application startup or configuration loading.

Why it matters to the business

Systems using the affected GNOME Maps version face risk of full host compromise through unauthenticated local or supply-chain file placement, though low EPSS and absence from KEV indicate limited observed exploitation over the 1124 days since publication.

How an attack unfolds

An attacker places a malicious service.json file containing injected commands in a location read by gnome-maps; when the application loads the file, the injected content executes with the privileges of the maps process, potentially establishing persistence or escalating access.

How to fix it

Upgrade gnome-maps to the fixed commit d26cd774d524404ef7784e6808f551de83de4bea or later; verify the update through git history or package manager before redeploying.

How to confirm the fix worked

Confirm the running version reports commit d26cd774d524404ef7784e6808f551de83de4bea or newer; test by attempting to load a benign service.json and verifying no unexpected process execution occurs.

Typical attack path

1. Identify or gain write access to a directory scanned for service.json by gnome-maps
2. Craft and drop a service.json file embedding shell commands or code payloads
3. Trigger gnome-maps execution or configuration reload to parse the file
4. Execute injected commands to achieve code execution and follow-on actions

How to detect it

Review application and system logs for unexpected process spawns or command executions immediately after gnome-maps startup; inspect service.json files in configuration directories for anomalous content or scripts.

What your security team should do

• Prioritize upgrade to the fixed commit across all deployments within standard change windows
• Audit service.json file locations and restrict write permissions to trusted users only
• Monitor EPSS trend and re-evaluate if new exploit code appears given the 13% score increase