GHSA-5fc3-pqf2-57cx — node-commons
Fix: apache/iotdb#14863GHSA-5fc3-pqf2-57cx is a Information Exposure vulnerability in org.apache.iotdb:node-commons. A fix is available for org.apache.iotdb:node-commons — see the affected versions and patch details below.
Apache IoTDB Discloses Sensitive Information via Log Files
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5fc3-pqf2-57cx.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
org.apache.iotdb:node-commons☕org.apache.iotdb:node-commons🐍apache-iotdb🐍apache-iotdbReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Exposure of Sensitive Information to an Unauthorized Actor, Insertion of Sensitive Information into Log File vulnerability in the OpenIdAuthorizer of Apache IoTDB.
This issue affects Apache IoTDB: from 0.10.0 through 1.3.3, from 2.0.1-beta before 2.0.2.
Users are recommended to upgrade to version 1.3.4 and 2.0.2, which fix the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.iotdb:node-commons | ≥ 0.10.0&&< 1.3.4 | 1.3.4org.apache.iotdb:node-commons:1.3.4 |
| ☕Maven | org.apache.iotdb:node-commons | ≥ 2.0.1-beta&&< 2.0.2 | 2.0.2org.apache.iotdb:node-commons:2.0.2 |
| 🐍PyPI | apache-iotdb | ≥ 0.10.0&&< 1.3.4 | 1.3.4pip install --upgrade 'apache-iotdb==1.3.4' |
| 🐍PyPI | apache-iotdb | ≥ 2.0.1b0&&< 2.0.2 | 2.0.2pip install --upgrade 'apache-iotdb==2.0.2' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.iotdb:node-commons, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.iotdb:node-commons to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5fc3-pqf2-57cx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5fc3-pqf2-57cx can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5fc3-pqf2-57cx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5fc3-pqf2-57cx in your dependencies?
O3 Security finds GHSA-5fc3-pqf2-57cx across Maven, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.