DEV Community

kozhevniko
kozhevniko

Posted on

AzuraCast's 2 App Matches and 14,742 Title Matches Describe Two Different Surfaces

AzuraCast's 2 App Matches and 14,742 Title Matches Describe Two Different Surfaces

AzuraCast combines a web radio control panel, public player pages, station roles, and an API. A single title search can surface both the operational console and the listener-facing side. Treating those matches as one asset population hides the credential boundary.

ZoomEye SDK probes on 22 November 2026 used sub_type=all, page 1, and pagesize=1. The exact query app="AzuraCast" returned 2 matches. title="AzuraCast" returned 14,742. The queries completed between 06:46 and 06:47 Asia/Shanghai.

The large difference is not evidence that 14,740 installations lack the application fingerprint. It means the two index fields describe different evidence. A title can be attached to a public station site, a login page, an API error page, or a reverse-proxy page. The app value is narrower and may be absent from many deployments.

Roles and API keys sit behind the title

AzuraCast supports role-based user management with global and per-station permissions. Each installation also exposes API documentation, and operators can create API keys from the web interface. A public player page may be harmless while the adjacent administration path can change playlists, mounts, users, or station configuration.

The project's changelog warns that allowing users to edit raw Liquidsoap configuration has security implications in multi-tenant environments because the scripting language can call external processes and read system files. That setting turns a station-level role into a much stronger authority over the host. An inventory that records only "AzuraCast exposed" misses this distinction.

Separate public from administrative reach

For each owned installation, record the web base path, API path, public player routes, admin routes, reverse-proxy rules, and TLS certificate. Confirm whether the API is reachable from the internet and which roles can create or use keys.

Expose public players deliberately. Put administration behind a VPN, access proxy, or tightly scoped network rule. Review global and per-station roles, remove unused API keys, and disable raw Liquidsoap editing unless a trusted administrator has a documented need. Keep station credentials out of public page source and client-side configuration.

Use the project's API documentation to enumerate active keys and permissions. A valid login does not establish least privilege. Rotate keys tied to former staff or decommissioned stations.

Read the count correctly

The 2 application matches are a narrow product signal. The 14,742 title matches are a broad web clue. Neither number proves vulnerability. Together they show why identity, route, and permission review must follow the measurement.

References

Top comments (0)