CVE-2017-18190

UnknownEPSS 2.98%

Last modified

CVE-2017-18190 is a vulnerability of currently unknown severity. A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS nor the web browser is responsible for ensuring that localhost.localdomain is 127.0.0.1).. EPSS estimates a 2.98% chance of exploitation in the next 30 days.

Description

A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS nor the web browser is responsible for ensuring that localhost.localdomain is 127.0.0.1).

Metrics

EPSS Probability
2.98%

85.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
AppleCups< 2.2.2
DebianDebian Linux7.0
DebianDebian Linux8.0
CanonicalUbuntu Linux14.04
CanonicalUbuntu Linux16.04

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2017-18190?
A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS nor the web browser is responsible for ensuring that localhost.localdomain is 127.0.0.1).
How severe is CVE-2017-18190?
Severity scoring for CVE-2017-18190 is pending analysis. The EPSS model estimates a 2.98% probability of exploitation in the next 30 days.
How do I fix CVE-2017-18190?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-18190?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST