TCC Bypass via Inherited Permissions in Bundled Interpreter in Inkscape.app
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Inkscape | Inkscape | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Apple | Macos | — |
| Inkscape | Inkscape | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.162% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apple
Apple macos Inkscape Inkscape inkscape |
|
| Vendors & Products |
Apple
Apple macos Inkscape Inkscape inkscape |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MacOS version of Inkscape bundles a Python interpreter that inherits the Transparency, Consent, and Control (TCC) permissions granted by the user to the main application bundle. An attacker with local user access can invoke this interpreter with arbitrary commands or scripts, leveraging the application's previously granted TCC permissions to access user's files in privacy-protected folders without triggering user prompts. Accessing other resources beyond previously granted TCC permissions will prompt the user for approval in the name of Inkscape, potentially disguising attacker's malicious intent. This issue has been fixed in 1.4.3 version of Inkscape. | |
| Title | TCC Bypass via Inherited Permissions in Bundled Interpreter in Inkscape.app | |
| Weaknesses | CWE-276 | |
| References |
| |
| Metrics |
cvssV4_0
|