LiveActive security incident?Get immediate response
CVE Record

CVE-2024-51395: Buffer Overflow vulnerability in Ardupiot Copter Latest commit 92693e023793133e49a035daf37c14433e484778 all...

Buffer Overflow vulnerability in Ardupiot Copter Latest commit 92693e023793133e49a035daf37c14433e484778 allows a local attacker to cause a denial of service via the AP_SmartAudio::loop, AP_SmartAudio, AP_SmartAudio.cpp components.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service risk in ArduPilot Copter SmartAudio handling. A local attacker could crash or disrupt affected software, which matters for operational availability but is not described as remote code execution or data theft.

Executive priority

Handle as a moderate operational availability issue. It deserves inventory and vendor-tracking now, especially for safety-sensitive deployments, but the provided evidence does not support emergency treatment for internet-wide exploitation.

Technical view

CVE-2024-51395 is reported as a CWE-121 stack buffer overflow in AP_SmartAudio::loop, AP_SmartAudio, and AP_SmartAudio.cpp in a referenced ArduPilot Copter commit. CVSS 3.1 is 6.2 with local attack vector and high availability impact only.

Likely exposure

Exposure appears limited to systems running the referenced ArduPilot Copter code path, but the CVE lists affected vendor, product, and versions as n/a. Treat fleets using ArduPilot Copter with SmartAudio-related functionality as candidates for review until vendor details clarify scope.

Exploitation context

The CVSS vector describes local, low-complexity, no-privilege, no-user-interaction exploitation causing high availability impact. The CVE is not in KEV, and the provided sources do not state active exploitation or public weaponized exploit availability.

Researcher notes

The public record is thin: affected product fields are n/a, and the main technical reference is a GitHub issue. Avoid broad product claims until maintainers clarify impacted branches, releases, and whether a patch exists.

Mitigation direction

  • Check ArduPilot issue and CVE records for maintainer guidance or fixed releases.
  • Inventory ArduPilot Copter builds and identify use of the referenced commit or SmartAudio code.
  • Limit local access to systems running affected autopilot software where operationally feasible.
  • Disable SmartAudio-related functionality only if supported and operationally acceptable.
  • Prioritize update testing once an official fix or release note is available.

Validation and detection

  • Confirm whether deployed builds include AP_SmartAudio.cpp from the referenced vulnerable commit.
  • Review configuration and hardware integrations for SmartAudio usage.
  • Monitor crash, reboot, or watchdog events on candidate systems.
  • Track the ArduPilot issue for scope clarification and remediation status.
  • Validate mitigations in a non-production flight or bench environment first.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

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-121: 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-51395 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

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

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: noTechnical 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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2024-51395Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

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-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.