Vulnerability in OreSat Firmware (CVE-2026-67673)
Summary
Vulnerability in OreSat Firmware (CVE-2026-67673). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A stack-based buffer overflow vulnerability exists in the cmd_edl function of OreSat Firmware v1.0. The vulnerability is triggered when processing the edl fw_flash command, where the argument is copied to a 64-byte stack buffer via memcpy without proper length validation. An attacker with physical access to the UART3 serial interface can exploit this vulnerability by sending a maliciously crafted command with an oversized filename parameter,
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-2026-67673 has been found in OreSat Firmware.
Risk of unauthorized operations or information disclosure. CVSS score: 4.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OreSat Firmware CVE-2026-67673" on the vendor's site.
CVE-2026-67673 (OreSat Firmware) — CWE-121 / CVSS v3 4.6
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.
A vulnerability (CWE-121) exists in OreSat Firmware.
Check the vendor advisory for the affected versions of OreSat Firmware.
Severity: Medium (CVSS 4.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OreSat Firmware を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web nvd.nist.gov
- web github.com