Security readout for executives and security teams
Plain-English summary
Back In Time 1.1.18 and earlier used an unsafe, deprecated Polkit authorization method. A local process could be checked as one user and then replaced before the privileged action completes, creating a privilege decision mismatch. The public sources do not provide CVSS, confirmed impact scope, or active exploitation evidence.
Executive priority
Treat as a targeted local privilege-risk issue, not an internet-wide emergency based on available evidence. Prioritize Linux endpoints or shared systems where untrusted local users can run applications.
Technical view
The vulnerable _checkPolkitPrivilege function in serviceHelper.py used Polkit unix-process authorization, which is prone to PID reuse time-of-check/time-of-use races because polkitd checks /proc/<pid>/status after the request. The flaw affects Back In Time 1.1.18 and earlier according to the CVE description.
Likely exposure
Exposure appears limited to systems with Back In Time/backintime 1.1.18 or earlier installed. The source bundle does not indicate remote exposure, default deployment prevalence, or affected operating-system packages.
Exploitation context
CISA KEV is false, and the provided sources do not state active exploitation. The vulnerability class suggests a local authorization race, but the bundle does not provide exploit prerequisites, reliability, or real-world abuse evidence.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPEs, or detailed advisory text were provided. The key technical signal is the deprecated Polkit unix-process race described by the CVE and the linked Back In Time commit.
Mitigation direction
- Inventory systems for Back In Time/backintime installations and versions.
- Prioritize removal or upgrade of versions 1.1.18 and earlier.
- Use vendor or distribution advisories to identify corrected packages.
- Review the linked upstream commit before accepting source-level remediation.
- Limit local user access on affected shared Linux systems where feasible.
Validation and detection
- Confirm Back In Time is absent or newer than 1.1.18.
- Check package manager records or SBOMs for backintime versions.
- Review serviceHelper.py for continued unix-process Polkit authorization use.
- Document any affected hosts pending vendor-confirmed remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-7572 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/bit-team/backintime/commit/7f208dc547f569b689c888103e3b593a48cd1869CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.