Nasa fprime
F´: FpySequencer Integer Overflow in Stack Offset/Size Validation Leading to Out-of-Bounds Write
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to 4.2.0, Svc::FpySequencer STORE directive stack write validation the bounds check adds attacker-controlled offset and size before memcpy, allowing integer wraparound to make an out-of-range destination appear valid. When a sequence-controlled STORE directive supplies a stack offset and size whose U32 sum wraps, memcpy can write outside the sequencer stack, causing memory corruption, denial of service, and potentially code execution. This issue is fixed in version 4.2.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 4.2.0
Fixed in 4.2.0
Mitigation
Upgrade fprime to 4.2.0 or later.
References
- Vendor advisory github.com/nasa/fprime/security/advisories/GHS…
- Patch github.com/nasa/fprime/pull/4534
- Patch github.com/nasa/fprime/commit/7527430d9ae7c88f…
1 more
- Release notes github.com/nasa/fprime/releases/tag/v4.2.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.