Path Traversal in iobroker.admin (CVE-2019-10765)
Summary
Path traversal in iobroker.admin (CVE-2019-10765). Successful exploitation can lead to full system takeover. Exploitable via iobroker.admin. Mitigation: upgrade to 3.6.12 or later.
Original description
The description as published by the source.
Versions of iobroker.admin prior to 3.6.12 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended folder in the /log/ route, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.
Recommendation
Upgrade to version 3.6.12 or later.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2019-10765 has been found in iobroker.admin.
Attackers can target a specific entry point like iobroker.admin over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade iobroker.admin to 3.6.12 or later.
If unsure, ask your IT team or search "iobroker.admin CVE-2019-10765" on the vendor's site.
CVE-2019-10765 (iobroker.admin) — CWE-22
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: iobroker.admin
Patched: 3.6.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in iobroker.admin. Attackers reach the vulnerable code path via iobroker.admin without authentication.
Check the vendor advisory for the affected versions of iobroker.admin. Attack surface: iobroker.admin.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.6.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'iobroker.admin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'iobroker.admin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
iobroker.adminを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade iobroker.admin to 3.6.12ステージング環境で 3.6.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web snyk.io
- web npmjs.com