LiveActive security incident?Get immediate response
CVE Record

CVE-2024-55045: Firmament-Autopilot FMT-Firmware commit de5aec was discovered to contain a buffer overflow via the task_mav...

Firmament-Autopilot FMT-Firmware commit de5aec was discovered to contain a buffer overflow via the task_mavobc_entry function at /comm/task_comm.c.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's Takehigh

Analyst readout for executives and security teams

Plain-English summary

CVE-2024-55045 is a high-severity buffer overflow reported in Firmament-Autopilot FMT-Firmware at commit de5aec. The issue is in task_mavobc_entry in /comm/task_comm.c. If reachable in deployed firmware, it could affect confidentiality, integrity, and availability at a limited level.

Executive priority

Treat this as a high-priority exposure review for any environment using Firmament-Autopilot firmware. Business urgency depends on whether the vulnerable code is deployed, reachable, and safety-relevant. Current public data is incomplete, so inventory confirmation is the first decision point.

Technical view

The CVE describes a CWE-120 buffer overflow in task_mavobc_entry within /comm/task_comm.c. CVSS 3.1 is 7.3 with network attack vector, low complexity, no privileges, and no user interaction. The record does not provide affected versions, CPEs, patch status, or exploit details.

Likely exposure

Exposure appears limited to organizations using or deriving firmware from Firmament-Autopilot FMT-Firmware around commit de5aec. The CVE record lists affected vendor, product, and versions as n/a, so asset matching requires repository and firmware provenance review.

Exploitation context

The source bundle does not show CISA KEV listing or evidence of active exploitation. The CVSS vector indicates the flaw may be network-reachable and unauthenticated, but the available sources do not describe a working exploit path.

Researcher notes

Key gaps are affected version range, fixed commit, triggering conditions, and runtime impact. The CVE provides only commit, file, function, CWE, and CVSS. Avoid assuming exploitability beyond the CVSS vector until upstream issue details or code review confirm reachability.

Mitigation direction

  • Check the GitHub issue and upstream repository for vendor guidance or fixes.
  • Identify deployed firmware built from or near commit de5aec.
  • Restrict network access to exposed autopilot communication interfaces where feasible.
  • Prioritize testing and update planning for safety-relevant or externally reachable deployments.

Validation and detection

  • Review firmware build manifests for Firmament-Autopilot FMT-Firmware commit de5aec.
  • Inspect /comm/task_comm.c for task_mavobc_entry presence in deployed source trees.
  • Track CVE and GitHub issue updates for affected version and patch clarification.
  • Confirm whether relevant communication interfaces are reachable from untrusted networks.
Prepared
Confidence
medium
Sources
3

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-55045 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2024-55045Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.