CVE-2018-6827: VOBOT CLOCK before 0.99.30 devices do not verify X.509 certificates from SSL servers, which allows man-in-the-

Q: How do I fix CVE-2018-6827?

vobot firmware: upgrade to 0.99.30. Exact commands for each OS are on this page.

Q: Is CVE-2018-6827 being exploited?

CVE-2018-6827 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-6827 affect?

CVE-2018-6827 affects vobot firmware. Severity is high (CVSS 8.1). VOBOT CLOCK before 0.99.30 devices do not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information, and consequently execute arbitrary code, via a crafted certifi

Q: How urgent is CVE-2018-6827?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.1REMOTEUPGRADE

CVE-2018-6827 is a high-severity flaw (CVSS 8.1) affecting vobot firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

VOBOT CLOCK before 0.99.30 devices do not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information, and consequently execute arbitrary code, via a crafted certificate, as demonstrated by leveraging a hardcoded --no-check-certificate Wget option.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-295
Published	2018-02-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: omninova

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-02-09 15:29 UTCPublished CVE record published
2026-06-17 02:02 UTCUpdated Record last modified

omninova vobot firmware UPGRADE

Affected: < 0.99.30

Fixed in: 0.99.30

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-6827?

vobot firmware: upgrade to 0.99.30. Exact commands for each OS are on this page.

Is CVE-2018-6827 being exploited?

CVE-2018-6827 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-6827 affect?

CVE-2018-6827 affects vobot firmware. Severity is high (CVSS 8.1). VOBOT CLOCK before 0.99.30 devices do not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information, and consequently execute arbitrary code, via a crafted certifi

How urgent is CVE-2018-6827?

Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2018-6826 HIGH 7.5 UPGRADE An issue was discovered on VOBOT CLOCK before 0.99.30 devices
CVE-2018-6825 CRITICAL 9.8 UPGRADE An issue was discovered on VOBOT CLOCK before 0.99.30 devices

References

← Back to latest CVEs