Little Snitch
Approved changes feed: RSS · Atom
cpe:2.3:a:objective_development:little_snitch:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Objective Development (a5ecd3b1-3633-584a-b46d-842679d96e70) |
|---|---|
| Product | Little Snitch (e5207d0c-c157-51bf-85cd-c9bab40a6dfc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-10470 |
vulnerable | 2026-06-08 05:10:26.684199 |
Details available
Little Snitch versions 4.0 to 4.0.6 use the SecStaticCodeCheckValidityWithErrors() function without the kSecCSCheckAllArchitectures flag and therefore do not validate all architectures stored in a fat binary. An attacker can maliciously craft a fat binary containing multiple architectures that may cause a situation where Little Snitch treats the running process as having no code signature at all while erroneously indicating that the binary on disk does have a valid code signature. This could lead to users being confused about whether or not the code signature is valid.
Published: 2018-06-12T17:00:00.000Z
Updated: 2024-09-16T21:03:03.661Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.