dbcve.org
Rt ThreadApplication

CVE-2024-25392

MEDIUM · 5.9 CVSS v3.1 Published 2024-03-27
Fix available
A fix is available. Upgrade to after 5.0.2 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges 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
An out-of-bounds access occurs in utilities/var_export/var_export.c in RT-Thread through 5.0.2.

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 · low confidence

An out-of-bounds memory access vulnerability exists in the var_export utility component of RT-Thread (an embedded real-time operating system). The flaw is located in utilities/var_export/var_export.c and allows memory access beyond allocated buffer boundaries, potentially leading to crashes or unpredictable behavior.

MitigationUpdate to a patched version of RT-Thread when available. Until then, restrict or disable the var_export utility in production deployments to minimize attack surface.

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
Rt ThreadApplication
Affected:<= 5.0.2

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

CVSS:3.1/AV:L/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 checks

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

  1. Check RT-Thread version in use
    Locate the version definition in your RT-Thread distribution. In the root directory or in a version header file (commonly found in include/rtdef.h or similar), find the RT_THREAD_VERSION constant or the version.txt file. Compare the version number to the affected range <= 5.0.2.
    Affected if The installed RT-Thread version is 5.0.2 or lower.
  2. Verify var_export component is enabled in build configuration
    Examine your build configuration files (such as Kconfig, .config, or defconfig files in your build directory). Search for any configuration option related to var_export, typically named RT_USING_VAR_EXPORT or similar. Check if this option is set to enabled (often denoted as 'y' or '=y').
    Affected if The var_export component is enabled (RT_USING_VAR_EXPORT or equivalent is set) in the build configuration.
  3. Confirm var_export source file is compiled
    Inspect your build output or object files directory. Look for var_export.c in the compiled objects, typically under the utilities/var_export path. Check if var_export.o or var_export.a exists in the build artifacts.
    Affected if The var_export.c source file is present and was compiled into the firmware or application binary.
  4. Check for var_export usage in application code
    Search your application source code for calls to var_export functions. Look for include statements referencing var_export.h and any function invocations such as var_export() or rt_var_export(). Review the source files in your project for these patterns.
    Affected if The application code includes var_export.h or calls var_export functions.

A system is affected if it runs RT-Thread version 5.0.2 or lower AND has the var_export utility component enabled and included in the build.

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 a release after 5.0.2
Interim mitigation

Update to a patched version of RT-Thread when available. Until then, restrict or disable the var_export utility in production deployments to minimize attack surface.

Recommended fix Moderate confidence

RT-Thread 5.1.0 or later stable release

  1. 1. Identify the current RT-Thread version in use by checking the version define in rtconfig.h or the version.h header file
  2. 2. Obtain the latest stable RT-Thread release (version 5.1.0 or later) from the official GitHub repository at github.com/RT-Thread/rt-thread
  3. 3. Review the release notes for version 5.1.0 to confirm the var_export.c vulnerability (CVE-2024-25392) has been addressed
  4. 4. Backup the current project configuration and any custom modifications to source files
  5. 5. Replace the rt-thread directory with the new version from the official repository
  6. 6. Re-apply any necessary custom configurations and driver implementations
  7. 7. Rebuild the project and verify all components compile successfully
  8. 8. Perform functional testing to ensure the system operates correctly with the updated version
Caveat Review migration notes as API changes between major versions may require code adjustments; custom board configurations may need updating

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

Fix this in Rt Thread Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25392 — 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-2024-25392 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