CVE-2025-47868
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 · uneditedOut-of-bounds Write resulting in possible Heap-based Buffer Overflow vulnerability was discovered in tools/bdf-converter font conversion utility that is part of Apache NuttX RTOS repository. This standalone program is optional and neither part of NuttX RTOS nor Applications runtime, but active bdf-converter users may be affected when this tool is exposed to external provided user data data (i.e. publicly available automation). This issue affects Apache NuttX: from 6.9 before 12.9.0. Users are recommended to upgrade to version 12.9.0, which fixes the issue.
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 heap-based buffer overflow vulnerability exists in the bdf-converter font conversion utility of Apache NuttX RTOS. The out-of-bounds write occurs when processing font data, potentially allowing remote code execution when the tool processes untrusted input.
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>= 6.9, < 12.9.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if Apache NuttX is in useCheck for NuttX source code directories, build artifacts, or firmware images that reference NuttX. Look for nuttx/ directory in build environments or config files mentioning 'nuttX' or 'CONFIG_ARCH_*' in defconfig files.Affected if NuttX source tree, build configuration, or firmware derived from NuttX is present in the environment
-
Determine the installed or built NuttX versionRun 'git -C /path/to/nuttX describe --tags' or check VERSION file in the NuttX source root. If working with a built firmware, extract and inspect the version string from the image or check the defconfig file for version identifiers.Affected if The version is >= 6.9 and < 12.9.0
-
Locate the bdf-converter utilitySearch for the bdf-converter binary or source file in the NuttX tree: 'find /path/to/nuttX -name "*bdf*" -o -name "*converter*" | grep -i font'. Check tools/bdf-converter directory if it exists in the source.Affected if The bdf-converter tool or its source code is present in the NuttX environment
-
Check if bdf-converter is built or configured for useExamine the NuttX configuration (defconfig or .config file) for font-related build options such as 'CONFIG_FONT' or 'CONFIG_NXTERM'. Check if the tools/bdf-converter directory was compiled into the build output.Affected if Font conversion tools are enabled in the NuttX configuration or the bdf-converter binary exists in the build output
-
Verify font data processing capabilityInspect whether the system processes external or user-supplied BDF font files. Check if there are paths where untrusted font data could be passed to bdf-converter or the font subsystem.Affected if The bdf-converter can process external font data or fonts from untrusted sources
The environment is affected if Apache NuttX version 6.9 through 12.8.x is in use and the bdf-converter font processing utility is present and capable of handling external font data.
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.
dbcve · scoped12.9.0
Upgrade to Apache NuttX version 12.9.0 or later. Until upgraded, restrict access to the bdf-converter utility and avoid processing externally-provided font data.
12.9.0
- 1. Verify current NuttX version by checking the version file or git tag in the local repository
- 2. Download Apache NuttX version 12.9.0 from the official Apache NuttX downloads (downloads.apache.org) or GitHub releases
- 3. Extract the new version archive to a clean directory
- 4. Locate the tools/bdf-converter utility in the new version
- 5. Replace or rebuild the bdf-converter binary in any automation, CI/CD pipelines, or systems that use this tool
- 6. Rebuild and redeploy any systems or images that incorporated the vulnerable bdf-converter utility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47868 — 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-2025-47868 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