dbcve.org
Freertos Plus TcpApplication · Amazon

CVE-2025-11616

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 4.3.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A missing validation check in FreeRTOS-Plus-TCP's ICMPv6 packet processing code can lead to an out-of-bounds read when receiving ICMPv6 packets of certain message types which are smaller than the expected size. These issues only affect applications using IPv6. Users should upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes.

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 confidence

A missing validation check in FreeRTOS-Plus-TCP's ICMPv6 packet processing allows out-of-bounds reads when receiving ICMPv6 packets smaller than the expected size for certain message types. This occurs because the code does not validate packet length before accessing memory offsets, leading to reads beyond buffer boundaries.

MitigationUpgrade to the latest FreeRTOS-Plus-TCP version to obtain the fix, and audit any forked or derivative code to ensure the validation check has been incorporated. Only IPv6-enabled applications are affected.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Freertos Plus TcpApplication
Affected:>= 4.0.0, < 4.3.4

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IPv6 is enabled in FreeRTOS-Plus-TCP
    Inspect FreeRTOSIPConfig.h for the configuration option 'ipconfigIPv6_ENABLED' or 'FREERTOS_PLUS_IPV6' and verify it is set to 1 or defined. Search for 'ipconfigIPv6_ENABLED' in your configuration header file.
    Affected if IPv6 is enabled (the defined value is 1 or the macro exists and is enabled)
  2. Identify the FreeRTOS-Plus-TCP version
    Check the version header or version definition in your FreeRTOS-Plus-TCP distribution. Look for a version file or header such as 'FreeRTOS_IP.h' or 'aws_version.h' that defines the version number (e.g., ipconfigMAJOR_VERSION, pdMS_TO_TICKS version macros, or a version string).
    Affected if The installed version is 4.0.0 or higher but lower than 4.3.4
  3. Locate ICMPv6 processing code
    Search the codebase for ICMPv6 handling functions such as 'ICMPv6_ProcessPacket', 'pricmpv6_parse_packet', or files named 'ICMPv6.c' or 'ICMPv6.h' within the FreeRTOS-Plus-TCP source directory.
    Affected if The ICMPv6 source files exist and are included in the build (this indicates IPv6 functionality is compiled)
  4. Check for packet length validation in ICMPv6 handler
    Examine the ICMPv6 packet processing function identified in step 3. Look for a bounds check on the ICMPv6 packet length (e.g., uxICMPv6Offset + sizeof( ICMPHeader_t ) > uxBufferLength or similar) before memory offset access. Search for accesses to memory offsets like 'pucICMPv6Buffer' or 'pICMPHeader' without prior length validation.
    Affected if No length/size validation is performed on the ICMPv6 packet before reading memory offsets, or the check is missing for specific message types

The environment is affected if IPv6 is enabled in the FreeRTOS-Plus-TCP configuration AND the installed version is >= 4.0.0 and < 4.3.4 AND the ICMPv6 packet handling code lacks proper buffer length validation before memory offset access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.3.4 or later
Fixed in 4.3.4
Interim mitigation

Upgrade to the latest FreeRTOS-Plus-TCP version to obtain the fix, and audit any forked or derivative code to ensure the validation check has been incorporated. Only IPv6-enabled applications are affected.

Recommended fix High confidence

4.3.4 or later (latest FreeRTOS-Plus-TCP release)

  1. 1. Identify the current FreeRTOS-Plus-TCP version in use by checking the version.h or version.c file in the FreeRTOS-Plus-TCP directory
  2. 2. Download or clone the latest FreeRTOS-Plus-TCP release from the official repository (github.com/FreeRTOS/FreeRTOS-Plus-TCP)
  3. 3. Replace the existing FreeRTOS-Plus-TCP files in your project with the files from version 4.3.4 or later
  4. 4. Ensure any local customizations or forks incorporate the new ICMPv6 validation fixes from the updated codebase
  5. 5. Rebuild and test the application, specifically validating IPv6 functionality to confirm the vulnerability is resolved
  6. 6. Verify that the application using IPv6 operates correctly with the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freertos Plus Tcp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11616 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11616 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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