dbcve.org
Revpi StatusApplication · Kunbus

CVE-2025-41646

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-06
Fix available
A fix is available. Upgrade to 2.4.6 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An unauthorized remote attacker can bypass the authentication of the affected software package by misusing an incorrect type conversion. This leads to full compromise of the device

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

This is a critical authentication bypass vulnerability where an incorrect type conversion flaw allows unauthenticated remote attackers to circumvent authentication mechanisms and gain full control of the affected device. The type conversion error enables attackers to circumvent proper credential validation.

MitigationApply vendor-supplied patches immediately; if no patch exists, review authentication code for type conversion issues between different data types (e.g., integer/boolean, string/enum) and implement strict type checking before authentication logic executes.

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
Revpi StatusApplication
Affected:< 2.4.6

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 if Kunbus Revpi Status is installed
    Locate Revpi Status software on the system - check for package installations, running processes, or services named revpi-status or related binaries
    Affected if Kunbus Revpi Status software is present on the system
  2. Determine installed version
    Query the installed version using system package management tools (dpkg, rpm) or software-specific version flags, compare against the affected range
    Affected if Installed version is below 2.4.6
  3. Verify authentication interface is exposed
    Check if Revpi Status web interface or API is network-accessible by reviewing listening ports and service configuration files
    Affected if Authentication interface is exposed to network access (even local)
  4. Confirm authentication is not bypassed locally
    Review authentication configuration files or settings for Revpi Status to verify proper credential validation is enabled and functioning
    Affected if Authentication can be bypassed due to the type conversion flaw

System is affected if Kunbus Revpi Status is installed with version below 2.4.6 and the authentication interface is network-accessible, allowing the type conversion flaw to be exploited for unauthenticated 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 2.4.6 or later
Fixed in 2.4.6
Interim mitigation

Apply vendor-supplied patches immediately; if no patch exists, review authentication code for type conversion issues between different data types (e.g., integer/boolean, string/enum) and implement strict type checking before authentication logic executes.

Recommended fix Moderate confidence

Revpi Status 2.4.6

  1. Check the official Kunbus support portal (psirt.kunbus.com or www.kunbus.com) for the Revpi Status version 2.4.6 release
  2. Download the Revpi Status 2.4.6 software package from the official Kunbus source
  3. Backup the current device configuration before performing the upgrade
  4. Upgrade Revpi Status to version 2.4.6 or later using the official upgrade procedure
  5. Verify the installation and confirm the version number after upgrade
  6. Test that the authentication mechanism is functioning correctly
Caveat Review release notes for any configuration or feature changes between your current version and 2.4.6

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

Fix this in Revpi Status Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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