Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-6666 low CVSS 2.0

Vulnerability in motogadget mo.lock Ignition Lock (CVE-2025-6666)

Summary

Vulnerability in motogadget mo.lock Ignition Lock (CVE-2025-6666). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A vulnerability was determined in motogadget mo.lock Ignition Lock up to 20251125. Affected by this vulnerability is an unknown functionality of the component NFC Handler. Executing manipulation can lead to use of hard-coded cryptographic key
. The physical device can be targeted for the attack. A high complexity level is associated with this attack. The exploitation appears to be difficult. The vendor was contacted early about this disclosure but did not respond in any way.

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-2025-6666 has been found in motogadget mo.lock Ignition Lock.
Risk of unauthorized operations or information disclosure. CVSS score: 2.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "motogadget mo.lock Ignition Lock CVE-2025-6666" on the vendor's site.

CVE-2025-6666 (motogadget mo.lock Ignition Lock) — CWE-320 / CVSS v3 2.0
Attack vector: physical / unauthenticated / 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-320) exists in motogadget mo.lock Ignition Lock.

📍 Affected scope

Check the vendor advisory for the affected versions of motogadget mo.lock Ignition Lock.

🔥 Severity

Severity: Low (CVSS 2.0/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・依存マニフェストで motogadget mo.lock Ignition Lock を使っているサービスとバージョンを洗い出す。

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

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

References

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