dbcve.org
OpenmptcprouterApplication

CVE-2025-65882

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to after 0.64 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 issue was discovered in openmptcprouter thru 0.64 in file common/package/utils/sys-upgrade-helper/src/tools/sysupgrade.c in function create_xor_ipad_opad allowing attackers to potentially write arbitrary files or execute arbitrary commands.

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 file write and potential command injection vulnerability exists in OpenMPTCPRouter's sys-upgrade-helper component. The create_xor_ipad_opad function in sysupgrade.c allows attackers to write arbitrary files or execute arbitrary commands, likely due to improper path validation or input sanitization when handling upgrade-related files.

MitigationUpgrade to a patched version of OpenMPTCPRouter beyond 0.64. If no patch is available, restrict network access to the sys-upgrade-helper functionality and audit the affected system for unauthorized changes.

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
OpenmptcprouterApplication
Affected:<= 0.64

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 OpenMPTCPRouter installation and version
    Check the installed OpenMPTCPRouter version using the system package manager or by examining the system information through the admin interface or command line (e.g., opkg list-installed | grep openmptcprouter or checking /etc/openmptcprouter_version)
    Affected if The installed version is 0.64 or lower
  2. Locate the sysupgrade.c file
    Search for the sysupgrade.c source file in the OpenMPTCPRouter installation directory or firmware build tree (common paths include /usr/src or the build system's package sources)
    Affected if The sysupgrade.c file exists and contains the create_xor_ipad_opad function
  3. Verify the vulnerable function exists
    Examine sysupgrade.c for the create_xor_ipad_opad function and inspect its input handling - look for parameters that accept user-controlled paths or data without proper validation
    Affected if The function accepts path or input parameters without sanitization checks (e.g., no validation of ../ sequences or shell metacharacters)
  4. Check if sysupgrade functionality is accessible
    Determine if the sysupgrade feature is enabled on the device - this may be accessible via the web interface, API endpoint, or command-line tool used for firmware updates
    Affected if The sysupgrade functionality is exposed and usable on the device
  5. Determine exposure to network
    Assess whether the sysupgrade interface is reachable from the network or requires local access - check firewall rules, web server bindings, and authentication requirements
    Affected if The sysupgrade interface is accessible remotely without strong access controls

A user is affected if they are running OpenMPTCPRouter version 0.64 or lower and the sysupgrade functionality with the vulnerable create_xor_ipad_opad function is accessible on their system.

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 0.64
Vendor patch github.com →
Interim mitigation

Upgrade to a patched version of OpenMPTCPRouter beyond 0.64. If no patch is available, restrict network access to the sys-upgrade-helper functionality and audit the affected system for unauthorized changes.

Recommended fix High confidence

OpenMPTCProuter 0.65 or later (any release after 0.64 containing the security fix)

  1. 1. Backup your current OpenMPTCProuter configuration before proceeding with any upgrade.
  2. 2. Download or access the latest OpenMPTCProuter release from the official GitHub repository at github.com/Ysurac/openmptcprouter.
  3. 3. Ensure you obtain version 0.65 or later (any version higher than 0.64).
  4. 4. Upgrade your OpenMPTCProuter installation to the fixed version using the standard upgrade procedure.
  5. 5. After upgrade, verify that the sys-upgrade-helper component has been updated by checking the version or reviewing the code changes from commit 09393d1c41a227bea7d5b85c0a06221b1302b25f.
  6. 6. Test that the sys-upgrade functionality works correctly without command injection vulnerabilities.
Caveat Review release notes for any configuration or feature changes between 0.64 and the target version before upgrading

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

Fix this in Openmptcprouter 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-65882 — 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-65882 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