How severe is CVE-2018-6892?

No CVSS score has been assigned to CVE-2018-6892 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2018-6892?

Affected package information for CVE-2018-6892 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2018-6892?

No fixed release is recorded for CVE-2018-6892 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2018-6892 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2018-6892 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2018-6892 actively exploited in the wild?

Yes. There are 12 known exploit references for CVE-2018-6892, including 5 documented proof-of-concept exploits on Exploit-DB and 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-6892?

CVE-2018-6892 has an EPSS (Exploit Prediction Scoring System) score of 93.4%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2018-6892?

CVE-2018-6892 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-6892 published, and has it been updated?

CVE-2018-6892 was published on February 11, 2018 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2018-6892

CVE-2018-6892 is a Buffer Overflow vulnerability. 12 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

An issue was discovered in CloudMe before 1.11.0. An unauthenticated remote attacker that can connect to the "CloudMe Sync" client application listening on port 8888 can send a malicious…

Published

Feb 11, 2018

Updated

Aug 5, 2024

Affected

1 product

Patched

See advisory

Exploits

12 known

Exploitation data as of Oct 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

93.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

An issue was discovered in CloudMe before 1.11.0. An unauthenticated remote attacker that can connect to the "CloudMe Sync" client application listening on port 8888 can send a malicious payload causing a buffer overflow condition. This will result in an attacker controlling the program's execution flow and allowing arbitrary code execution.

Affected Products

1 product · 1 configurations

Application

synccloudme

≤ 1.10.9

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46250remotewindows_x86-64

CloudMe Sync 1.11.2 Buffer Overflow - WoW64 (DEP Bypass)

by Matteo Malvica · Jan 28, 2019

Exploit-DB Source

EDB-45197remotewindows_x86-64

Cloudme 1.9 - Buffer Overflow (DEP) (Metasploit)

by Raymond Wellnitz · Aug 14, 2018

Exploit-DB Source

EDB-44027remotewindows✓ Verified

CloudMe Sync < 1.11.0 - Buffer Overflow

by hyp3rlinx · Feb 13, 2018

Exploit-DB Source

EDB-44175remotewindows✓ Verified

CloudMe Sync 1.10.9 - Stack-Based Buffer Overflow (Metasploit)

by Metasploit · Feb 26, 2018

Exploit-DB Source

EDB-48840localwindows

CloudMe 1.11.2 - Buffer Overflow ROP (DEP_ASLR)

by boku · Sep 29, 2020

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2018-6892 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-6892 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2018-6892

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2018-6892 in your dependencies?