No. Junglewise Threat Intelligence has no report of CVE-2018-18855 being exploited in the wild.
How severe is CVE-2018-18855?
Informational severity, published 28 June 2022.
Which products and versions are affected?
io.spray:spray-json_2.10 (Maven) ECOSYSTEM:introduced=0,fixed=1.3.5; io.spray:spray-json_2.11 (Maven) ECOSYSTEM:introduced=0,fixed=1.3.5; io.spray:spray-json_2.11.0-RC4 (Maven) ECOSYSTEM:introduced=0; io.spray:spray-json_2.12 (Maven) ECOSYSTEM:introduced=0,fixed=1.3.5; and 8 more.
Is there a fix for CVE-2018-18855?
Yes. io.spray:spray-json_2.10 (Maven): upgrade to 1.3.5 or later; io.spray:spray-json_2.11 (Maven): upgrade to 1.3.5 or later; io.spray:spray-json_2.12 (Maven): upgrade to 1.3.5 or later; io.spray:spray-json_2.13.0-M5 (Maven): upgrade to 1.3.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-18855?
Check whether you run io.spray:spray-json_2.10 (Maven), io.spray:spray-json_2.11 (Maven), io.spray:spray-json_2.11.0-RC4 (Maven) or one of the others listed 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
io.spray:spray-json_2.10 (Maven): upgrade to 1.3.5 or later
# set io.spray:spray-json_2.10 to 1.3.5 in your pom.xml or build.gradle
io.spray:spray-json_2.11 (Maven): upgrade to 1.3.5 or later
# set io.spray:spray-json_2.11 to 1.3.5 in your pom.xml or build.gradle
io.spray:spray-json_2.12 (Maven): upgrade to 1.3.5 or later
# set io.spray:spray-json_2.12 to 1.3.5 in your pom.xml or build.gradle
io.spray:spray-json_2.13.0-M5 (Maven): upgrade to 1.3.5 or later
# set io.spray:spray-json_2.13.0-M5 to 1.3.5 in your pom.xml or build.gradle