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

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

backintime: upgrade to newer than 1.1.18. Exact commands for each OS are on this page.

Q: Is CVE-2017-7572 being exploited?

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

CVE-2017-7572 affects backintime. Severity is high (CVSS 8.1). The _checkPolkitPrivilege function in serviceHelper.py in Back In Time (aka backintime) 1.1.18 and earlier uses a deprecated polkit authorization method (unix-process) that is subject to a race condition (time of check, time of use). With t

Q: How urgent is CVE-2017-7572?

Priority 50/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

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

The _checkPolkitPrivilege function in serviceHelper.py in Back In Time (aka backintime) 1.1.18 and earlier uses a deprecated polkit authorization method (unix-process) that is subject to a race condition (time of check, time of use). With this authorization method, the owner of a process requesting a polkit operation is checked by polkitd via /proc/<pid>/status, by which time the requesting process may have been replaced by a different process wi

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-362
Published	2017-04-06
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-04-06 18:59 UTCPublished CVE record published
2026-06-17 01:24 UTCUpdated Record last modified

backintime project backintime UPGRADE

Affected: <= 1.1.18

Fixed in: newer than 1.1.18

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.1.18 (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-7572?

backintime: upgrade to newer than 1.1.18. Exact commands for each OS are on this page.

Is CVE-2017-7572 being exploited?

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

CVE-2017-7572 affects backintime. Severity is high (CVSS 8.1). The _checkPolkitPrivilege function in serviceHelper.py in Back In Time (aka backintime) 1.1.18 and earlier uses a deprecated polkit authorization method (unix-process) that is subject to a race condition (time of check, time of use). With t

How urgent is CVE-2017-7572?

Priority 50/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

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

References

← Back to latest CVEs