Is CVE-2019-10765 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-10765 being exploited in the wild.

How severe is CVE-2019-10765?

Low severity, with a CVSS score of 3.1, published 4 September 2020.

Which products and versions are affected?

iobroker.admin (npm) SEMVER:introduced=0,fixed=3.6.12.

Is there a fix for CVE-2019-10765?

Yes. iobroker.admin (npm): upgrade to 3.6.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2019-10765 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2019-10765?

Check whether you run iobroker.admin (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2019-10765: ioBroker Admin path traversal in /log/ route

CVE-2019-10765 · Severity: low · CVSS 3.1 · Published 2020-09-04

ioBroker Admin is a web-based configuration and administration interface for the ioBroker home automation platform. The software contains a path traversal vulnerability in its log file handling that allows attackers to read and write arbitrary files on the server. Although authentication is normally required, it is disabled by default, putting unprotected systems at immediate risk of data theft and system compromise.

Vendors: npm.

Quick answers

Is CVE-2019-10765 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2019-10765 being exploited in the wild.
How severe is CVE-2019-10765?: Low severity, with a CVSS score of 3.1, published 4 September 2020.
Which products and versions are affected?: iobroker.admin (npm) SEMVER:introduced=0,fixed=3.6.12.
Is there a fix for CVE-2019-10765?: Yes. iobroker.admin (npm): upgrade to 3.6.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2019-10765 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2019-10765?: Check whether you run iobroker.admin (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

iobroker.admin (npm): upgrade to 3.6.12 or later
```
npm install iobroker.admin@3.6.12
```

Technical details

The vulnerability is a path traversal (CWE-22) flaw in the /log/ route of ioBroker Admin versions prior to 3.6.12. The application fails to properly restrict access to directories outside the intended logging folder, allowing attackers to manipulate file paths using directory traversal sequences (e.g., ../) to access arbitrary files. An attacker can read sensitive files (confidentiality impact) or write malicious files (integrity impact) on the system. Authentication is required in principle, but is disabled by default in many deployments, effectively removing this precondition. The vulnerability was patched in version 3.6.12 with log path sanitization as documented in commit 16b2b32.

Affected products

ioBroker Admin <3.6.12

Identifiers

CVE-2019-10765
GHSA-54xj-q58h-9x57

Timeline

2019-10-09: disclosed: Path traversal vulnerability disclosed; patch released in version 3.6.8
2019-10-09: patched: Log paths were sanitized in version 3.6.8, with final fix in 3.6.12
2020-09-04: advisory: GHSA advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.