dbcve.org
Command InjectionWeakness · CWE-77

CVE-2023-49565

HIGH · 8.4 CVSS v3.1 Published 2025-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The cbis_manager Podman container is vulnerable to remote command execution via the /api/plugins endpoint. Improper sanitization of the HTTP Headers X-FILENAME, X-PAGE, and X-FIELD allows for command injection. These headers are directly utilized within the subprocess.Popen Python function without adequate validation, enabling a remote attacker to execute arbitrary commands on the underlying system by crafting malicious header values within an HTTP request to the affected endpoint. The web service executes with root privileges within the container environment, the demonstrated remote code execution permits an attacker to acquire elevated privileges for the command execution. Restricting access to the management network with an external firewall can partially mitigate this risk.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The cbis_manager Podman container contains a command injection vulnerability in the /api/plugins endpoint. The X-FILENAME, X-PAGE, and X-FIELD HTTP headers are passed directly to Python's subprocess.Popen function without sanitization, allowing remote attackers to inject arbitrary shell commands. Since the web service runs as root within the container, successful exploitation grants attackers elevated privileges on the underlying system.

MitigationThe primary remediation is implementing proper input validation and sanitization on the affected HTTP headers before they're used in subprocess calls. The container should also be reconfigured to run with least privilege rather than root. Network access restrictions via firewall provide partial mitigation but do not address the root cause.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if cbis_manager container is running
    Run 'podman ps -a --filter name=cbis_manager' or 'docker ps -a --filter name=cbis_manager' to list containers with cbis_manager in the name
    Affected if A container with 'cbis_manager' in its name is present and running (status shows 'Up')
  2. Check the exposed network ports for the container
    Run 'podman inspect <container_id> --format "{{.NetworkSettings.Ports}}"' or check the container's port mappings via 'podman port <container_id>'
    Affected if Port mappings exist that expose the container's web service to the host or network (particularly the port serving the /api/plugins endpoint)
  3. Verify if the container runs as root
    Run 'podman inspect <container_id> --format "{{.Config.User}}"' to check the user the container executes as
    Affected if The output is empty, shows 'root', or shows no explicit non-root user configuration (indicating default root execution)
  4. Confirm the /api/plugins endpoint exists
    Attempt a harmless HTTP request to the container's web service at the /api/plugins path (e.g., curl -k http://<container_ip>:<port>/api/plugins)
    Affected if The endpoint responds (even with an error response) indicating it exists and processes requests with the vulnerable headers

A user is affected if they are running a cbis_manager container with the /api/plugins endpoint exposed and the container executes as root, allowing the X-FILENAME, X-PAGE, or X-FIELD headers to trigger arbitrary command execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

The primary remediation is implementing proper input validation and sanitization on the affected HTTP headers before they're used in subprocess calls. The container should also be reconfigured to run with least privilege rather than root. Network access restrictions via firewall provide partial mitigation but do not address the root cause.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-49565 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-49565 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data