Approved changes feed: RSS · Atom
cpe:2.3:a:nasa:fprime:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Nasa (53a37713-6109-50d8-8bfa-fbb4eca64abd) |
|---|---|
| Product | Fprime (1f029ebd-3305-5ff3-b9f6-7cfc1affdb16) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/nasa/fprime |
purl2cpe | 2026-06-01 10:15:37.572682 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-41144 |
vulnerable | 2026-06-08 08:03:14.960332 |
F´ (F Prime) has Integer Overflow in FileUplink
NONE
F´ (F Prime) is a framework that enables development and deployment of spaceflight and other embedded software applications. Prior to version 4.2.0, the bounds check byteOffset + dataSize > fileSize uses U32 addition that wraps around on overflow. An attacker-crafted DataPacket with byteOffset=0xFFFFFF9C and dataSize=100 overflows to 0, bypassing the check entirely. The subsequent file write proceeds at the original ~4GB offset. Additionally, Svc/FileUplink/File.cpp:20-31 performs no sanitization on the destination file path. Combined, these allow writing arbitrary data to any file at any offset. The impact is arbitrary file write leading to remote code execution on embedded targets. Note that this is a logic bug. ASAN does not detect it because all memory accesses are within valid buffers — the corruption occurs in file I/O. Version 4.2.0 contains a patch. No known workarounds are available.
Published: 2026-04-21T23:58:11.855Z
Updated: 2026-04-22T18:15:17.297Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.