Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49447 medium CVSS 5.3

Authentication Bypass in github.com/azukaar/cosmos-server (CVE-2026-49447)

Summary

Authentication bypass in github.com/azukaar/cosmos-server (CVE-2026-49447). Risk of unauthorized operations or information disclosure. Exploitable via GET /cosmos/api/constellation/public-devices. Mitigation: upgrade to 0.22.19 or later.

Original description

The description as published by the source.

Summary

GET /cosmos/api/constellation/public-devices discloses Constellation device metadata to a requester that supplies any non-empty Authorization header. The handler strips the string Bearer from the header but never validates the resulting token and never uses it in the database query.

This was confirmed locally by routing a request through the real tokenMiddleware with Authorization: Bearer not-a-real-token. The request returned public Constellation device metadata from a disposable fixture. A missing-header negative control returned 401 Unauthorized, proving the bypass is specifically the acceptance of arbitrary bearer values.

Details

Source-to-sink path:

  • src/httpServer.go:690 registers /api/constellation/public-devices on the authenticated admin API router.
  • src/httpServer.go:815-817 applies SecureAPI(..., public=false, ...), which runs tokenMiddleware.
  • src/httpServer.go:231-237 only treats Authorization: Bearer cosmos_... as a Cosmos API token for validation. Other bearer strings are not validated by the middleware and fall through to the handler.
  • src/constellation/api_devices_public.go:42-47 checks only that the Authorization header is present.
  • src/constellation/api_devices_public.go:49-50 strips Bearer but does not verify the token or compare it with a device/API key.
  • src/constellation/api_devices_public.go:63-67 queries all non-blocked and non-invisible devices without including the stripped auth value in…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49447 has been found in github.com/azukaar/cosmos-server.
Attackers can target a specific entry point like GET /cosmos/api/constellation/public-devices over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/azukaar/cosmos-server to 0.22.19 or later.
If unsure, ask your IT team or search "github.com/azukaar/cosmos-server CVE-2026-49447" on the vendor's site.

CVE-2026-49447 (github.com/azukaar/cosmos-server) — CWE-287 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /cosmos/api/constellation/public-devices / Authorization / tokenMiddleware / utils.CheckPermissions
Patched: 0.22.19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in github.com/azukaar/cosmos-server. Attackers reach the vulnerable code path via GET /cosmos/api/constellation/public-devices without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/azukaar/cosmos-server. Attack surface: GET /cosmos/api/constellation/public-devices / Authorization / tokenMiddleware / utils.CheckPermissions.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.22.19.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /cosmos/api/constellation/public-devices requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/azukaar/cosmos-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/azukaar/cosmos-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/azukaar/cosmos-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /cosmos/api/constellation/public-devices' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /cosmos/api/constellation/public-devices への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/azukaar/cosmos-server to 0.22.19

    ステージング環境で 0.22.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /cosmos/api/constellation/public-devices on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/azukaar/cosmos-server
[{"type":"SEMVER","events":[{"introduced":"0.22.18"},{"fixed":"0.22.19"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details