Categories
CVE-2023-37366 low CVSS 2.8

Vulnerability in Samsung Exynos Mobile Processor (CVE-2023-37366)

Summary

Vulnerability in Samsung Exynos Mobile Processor (CVE-2023-37366). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

In cd_parseMsg of cd_codec.c, there is a possible infinite loop due to improper input validation. This could lead to remote denial of service by a rogue cellular base station with no additional execution privileges needed. User interaction is not needed for exploitation.

Source: NIST National Vulnerability Database 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-2023-37366 has been found in Samsung Exynos Mobile Processor.
Risk of unauthorized operations or information disclosure. CVSS score: 2.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Samsung Exynos Mobile Processor CVE-2023-37366" on the vendor's site.

CVE-2023-37366 (Samsung Exynos Mobile Processor) — CWE-835 / CVSS v3 2.8
Attack vector: local / no user interaction
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

A vulnerability (CWE-835) exists in Samsung Exynos Mobile Processor.

📍 Affected scope

Check the vendor advisory for the affected versions of Samsung Exynos Mobile Processor.

🔥 Severity

Severity: Low (CVSS 2.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Samsung Exynos Mobile Processor を使っているサービスとバージョンを洗い出す。

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

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

Affected packages

Android :unknown:
[{"type":"ECOSYSTEM","events":[{"introduced":"Pixel-family specific:0"},{"fixed":"Pixel-family specific:2023-12-05"}]}]

References

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