Categories
CVE-2021-23803

Authorization Flaw in latte/latte (CVE-2021-23803)

Summary

Vulnerability in latte/latte (CVE-2021-23803). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.10.6 or later.

Original description

The description as published by the source.

This affects the package latte/latte before 2.10.6. There is a way to bypass allowFunctions that will affect the security of the application. When the template is set to allow/disallow the use of certain functions, adding control characters (x00-x08) after the function will bypass these restrictions.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2021-23803 has been found in latte/latte.
Successful exploitation can lead to full system takeover.
What to do: upgrade latte/latte to 2.10.6 or later.
If unsure, ask your IT team or search "latte/latte CVE-2021-23803" on the vendor's site.

CVE-2021-23803 (latte/latte) — CWE-863
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.10.6 — 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

Incorrect authorization (CWE-863) exists in latte/latte.

📍 Affected scope

Check the vendor advisory for the affected versions of latte/latte.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.10.6.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'latte/latte' . 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 'latte/latte' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade latte/latte to 2.10.6

    ステージング環境で 2.10.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

Packagist latte/latte
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.10.6"}]}]

References

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