dbcve.org
SpimApplication · Spimsimulator

CVE-2025-29365

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to after 9.1.24 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
spimsimulator spim v9.1.24 and before is vulnerable to Buffer Overflow in READ_STRING_SYSCALL.

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

spim simulator versions 9.1.24 and earlier contain a buffer overflow vulnerability in the READ_STRING_SYSCALL function. The function fails to properly validate input string length before copying data into a fixed-size buffer, allowing an attacker to overflow the buffer and potentially achieve arbitrary code execution with the privileges of the simulator process.

MitigationUpgrade spim to a version newer than v9.1.24. If immediate upgrading is not feasible, implement input length validation and bounds checking on all string inputs to READ_STRING_SYSCALL, and consider running the simulator in an isolated environment with restricted privileges.

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
SpimApplication
Affected:<= 9.1.24

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
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 checks

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

  1. Identify installed spim version
    Run `spim --version` or check your package manager for the installed spim package version
    Affected if The reported version is 9.1.24 or earlier
  2. Check for spim executable
    Run `which spim` to locate the spim binary, then run it with `--version` flag to confirm the version
    Affected if The version displayed is 9.1.24 or lower
  3. Determine if READ_STRING_SYSCALL is reachable
    Review any MIPS assembly code or scripts you run with spim to see if they invoke syscall 8 (read string) or similar string input syscalls that would trigger the vulnerable function
    Affected if Your spim workflow includes code that reads string input from users or files through spim syscalls

You are affected if your installed spim version is 9.1.24 or earlier and you run MIPS code that uses string input syscalls processed by READ_STRING_SYSCALL.

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.

From vendor data
Upgrade available Upgrade to a release after 9.1.24
Interim mitigation

Upgrade spim to a version newer than v9.1.24. If immediate upgrading is not feasible, implement input length validation and bounds checking on all string inputs to READ_STRING_SYSCALL, and consider running the simulator in an isolated environment with restricted privileges.

Fix this in Spim Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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