CVE-2017-16667: backintime (aka Back in Time) before 1.1.24 did improper escaping/quoting of file paths used as arguments to t

Q: How do I fix CVE-2017-16667?

backintime: upgrade to 1.1.24. Exact commands for each OS are on this page.

Q: Is CVE-2017-16667 being exploited?

CVE-2017-16667 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-2017-16667 affect?

CVE-2017-16667 affects backintime. Severity is high (CVSS 7.8). 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/plu

This month

HIGH 7.8UPGRADE

CVE-2017-16667 is a high-severity flaw (CVSS 7.8) affecting backintime. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-78
Published	2017-11-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: backintime project

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

Am I affected?

Timeline

2017-11-08 18:29 UTCPublished CVE record published
2026-06-17 01:09 UTCUpdated Record last modified

backintime project backintime UPGRADE

Affected: < 1.1.24

Fixed in: 1.1.24

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy backintime || rpm -q backintime || backintime --version

2. UPGRADE to 1.1.24 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade backintime

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade backintime

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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

backintime: upgrade to 1.1.24. Exact commands for each OS are on this page.

Is CVE-2017-16667 being exploited?

CVE-2017-16667 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-2017-16667 affect?

CVE-2017-16667 affects backintime. Severity is high (CVSS 7.8). 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/plu

How urgent is CVE-2017-16667?

Priority 46/100. High severity

Related CVEs

CVE-2017-7572 HIGH 8.1 UPGRADE The _checkPolkitPrivilege function in serviceHelper.py in Back In Time (aka backintime) 1.1.18 and earlier use

References

← Back to latest CVEs