Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-67269 high CVSS 7.5

Vulnerability in Gpsd Project (CVE-2025-67269)

Summary

Vulnerability in Gpsd Project (CVE-2025-67269). Risk of unauthorized operations or information disclosure. Exploitable via ffa1d6f40bca0b035fc7f5e563160ebb67199da7.

Original description

The description as published by the source.

An integer underflow vulnerability exists in the nextstate() function in gpsd/packet.c of gpsd versions prior to commit ffa1d6f40bca0b035fc7f5e563160ebb67199da7. When parsing a NAVCOM packet, the payload length is calculated using lexer->length = (size_t)c - 4 without checking if the input byte c is less than 4. This results in an unsigned integer underflow, setting lexer->length to a very large value (near SIZE_MAX). The parser then enters a loop attempting to consume this massive number of bytes, causing 100% CPU utilization and a Denial of Service (DoS) condition.

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-67269 has been found in Gpsd Project.
Attackers can target a specific entry point like ffa1d6f40bca0b035fc7f5e563160ebb67199da7 over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Gpsd Project CVE-2025-67269" on the vendor's site.

CVE-2025-67269 (Gpsd Project) — CWE-191 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ffa1d6f40bca0b035fc7f5e563160ebb67199da7 / SIZE_MAX
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-191) exists in Gpsd Project. Attackers reach the vulnerable code path via ffa1d6f40bca0b035fc7f5e563160ebb67199da7 without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Gpsd Project. Attack surface: ffa1d6f40bca0b035fc7f5e563160ebb67199da7 / SIZE_MAX.

🔥 Severity

Severity: High (CVSS 7.5/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・依存マニフェストで Gpsd Project を使っているサービスとバージョンを洗い出す。

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

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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