IotdbApplication · Apache
CVE-2025-48459
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 · uneditedDeserialization of Untrusted Data vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 2.0.5. Users are recommended to upgrade to version 2.0.5, 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 confidenceApache IoTDB versions 1.0.0 through 2.0.4 contain a deserialization vulnerability where untrusted data is being deserialized, potentially allowing remote code execution or other attacks depending on the deserialization handlers present in the application.
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
IotdbApplication
>= 1.0.0, < 2.0.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 the installed Apache IoTDB versionRun 'iotdb --version' from the command line, or check the version file in the IoTDB installation directory (commonly VERSION.txt in the root install folder)Affected if The version is 1.0.0 through 2.0.4 inclusive
-
Verify if IoTDB network services are listeningRun 'netstat -tlnp | grep iotdb' or 'ss -tlnp | grep iotdb' to see if IoTDB is listening on TCP ports (default ports: 6667 for RPC, 31999 for Thrift, 8080 for REST)Affected if IoTDB is listening on exposed network ports and the version is in the affected range
-
Check if RPC or Thrift service is enabledExamine the IoTDB configuration file (iotdb-config.properties or iotdb-system.properties) for 'rpc_port', 'thrift_port', or 'enable_rpc' settingsAffected if RPC or Thrift services are enabled and the version is in the affected range
-
Confirm REST API exposureCheck the IoTDB configuration for 'rest_port' (default 8080 or 18080) and verify if REST service is enabledAffected if REST API is enabled and accessible, and the version is in the affected range
The environment is affected if Apache IoTDB version 1.0.0 through 2.0.4 is installed and any network service (RPC, Thrift, or REST) that accepts serialized data is exposed or enabled.
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 · scoped2.0.5
Upgrade to Apache IoTDB version 2.0.5 which contains the fix for this deserialization vulnerability.
2.0.5
- Identify all Apache IoTDB instances running versions >= 1.0.0 and < 2.0.5 in your environment
- Review the Apache IoTDB 2.0.5 release notes and upgrade documentation for any migration requirements
- Create a complete backup of existing IoTDB data and configuration files
- Test the upgrade in a non-production environment first
- Stop the IoTDB service before upgrading
- Upgrade IoTDB to version 2.0.5 following the official upgrade procedure
- Verify the installation by checking the version number
- Restart the IoTDB service
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Iotdb
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48459 — 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-48459 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