CVE-2024-55045
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFirmament-Autopilot FMT-Firmware commit de5aec was discovered to contain a buffer overflow via the task_mavobc_entry function at /comm/task_comm.c.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA buffer overflow vulnerability exists in Firmament-Autopilot FMT-Firmware in the task_mavobc_entry function within /comm/task_comm.c (commit de5aec). This flaw allows an attacker to overwrite adjacent memory boundaries by overflowing a fixed-size buffer, potentially enabling code execution, denial of service, or data corruption on the embedded autopilot system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FMT-Firmware installationLocate the Firmament-Autopilot FMT-Firmware installation directory and confirm the presence of the /comm/task_comm.c fileAffected if The file /comm/task_comm.c is not found in the installation, indicating the product may not be present or uses a different codebase structure
-
Check commit version of task_comm.cExamine the git commit hash of task_comm.c or check the firmware version metadata. Look for commit de5aec or versions predating the fixAffected if The installed task_comm.c matches commit de5aec or an earlier vulnerable version
-
Locate the task_mavobc_entry functionSearch the task_comm.c file for the function definition: task_mavobc_entryAffected if The function task_mavobc_entry exists in the codebase, indicating the vulnerable code path is present
-
Inspect buffer operations in the functionReview the task_mavobc_entry function code for fixed-size buffer declarations and data copying operations (such as memcpy, strcpy, or similar functions) that lack explicit bounds checkingAffected if The function contains buffer write operations without proper size validation against buffer capacity
-
Verify mavobc communication is enabledCheck if the MAVLink OBC (Onboard Computer) communication module or task_mavobc_entry is configured to run in the firmware build or runtime configurationAffected if The task_mavobc_entry function is compiled and actively running on the autopilot system
The environment is affected if FMT-Firmware is installed with task_comm.c at commit de5aec or earlier, the task_mavobc_entry function is present with unbounded buffer operations, and the mavobc communication module is enabled in the build configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper bounds checking and use safe memory copy functions (e.g., memcpy_s, strncpy_s) with explicit length validation before writing data into buffers. Additionally, validate all input sizes against buffer dimensions prior to data copying operations.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55045 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-55045 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data