CVE-2017-16667

Name: CVE-2017-16667
Creator: NVD / NIST
Published: 2017-11-08T18:29:00.247+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.46%

Last modified Jun 17, 2026

CVE-2017-16667 is a vulnerability of currently unknown severity. backintime (aka Back in Time) before 1.1.24 did improper escaping/quoting of file paths used as arguments to the 'notify-send' command, leading to some parts of file paths being executed as shell commands within an os.system call in qt4/plugins/notifyplugin.py. This could allow an attacker to craft an unreadable file with a specific name to run arbitrary shell commands.. EPSS estimates a 1.46% chance of exploitation in the next 30 days.

Description

backintime (aka Back in Time) before 1.1.24 did improper escaping/quoting of file paths used as arguments to the 'notify-send' command, leading to some parts of file paths being executed as shell commands within an os.system call in qt4/plugins/notifyplugin.py. This could allow an attacker to craft an unreadable file with a specific name to run arbitrary shell commands.

Metrics

EPSS Probability

1.46%

70.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-78

Affected Software

Vendor	Product	Versions
Backintime Project	Backintime	< 1.1.24

References

https://github.com/bit-team/backintime/commit/cef81d0da93ff601252607df3db1a48f7f6f01b3Patch, Third Party Advisory
https://github.com/bit-team/backintime/issues/834Third Party Advisory
https://github.com/bit-team/backintime/releases/tag/v1.1.24Release Notes, Third Party Advisory
https://security.gentoo.org/glsa/201801-06Third Party Advisory
https://github.com/bit-team/backintime/commit/cef81d0da93ff601252607df3db1a48f7f6f01b3Patch, Third Party Advisory
https://github.com/bit-team/backintime/issues/834Third Party Advisory
https://github.com/bit-team/backintime/releases/tag/v1.1.24Release Notes, Third Party Advisory
https://security.gentoo.org/glsa/201801-06Third Party Advisory

Timeline

Published: Nov 8, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-16667?

How severe is CVE-2017-16667?

Severity scoring for CVE-2017-16667 is pending analysis. The EPSS model estimates a 1.46% probability of exploitation in the next 30 days.

How do I fix CVE-2017-16667?

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-16667?

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

Scan your code now

Source: NVD / NIST