Approved changes feed: RSS · Atom
cpe:2.3:a:ilbers:isar:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Ilbers (83a5d720-7950-58e9-ad8a-1bca12ffc3c6) |
|---|---|
| Product | Isar (311258e0-6890-5127-909e-3bb05d92c83c) |
| 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-2026-55222 |
vulnerable | 2026-11-03 10:16:34.517106 |
Isar: Unprivileged user ownership of trusted repository GPG public keys storage after bootstrap
MEDIUM (5.1)
Isar is an integration system for automated root filesystem generation. In versions 0.11 and newer, /etc/apt/trusted.gpg.d is created manually during bootstrap setup to be able to deploy local keys. By that, the directory is owned by the calling user (the one that executes Isar) instead of root. If the calling user's id is identical to one of an unprivileged user inside the image, this user is able to alter existing keys and deploy new ones, silently breaking the apt repo integrity protection. The issue is has no impact on those images that use an immutable rootfs, or if apt is never invoked. Changing only the keys does not trigger an exploit, it's just one step in a chain. An attacker would also have to manipulate a remote repo or intercept non-secure communication with it. This issue has been patched via commit 29e84ed.
Published: 2026-10-23T14:31:41.863Z
Updated: 2026-10-23T20:57:39.282Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-65100 |
vulnerable | 2026-06-08 07:39:20.710444 |
Security Snapshot May Use Unintended Timestamp When Only ISAR_APT_SNAPSHOT_DATE Is Set
Isar is an integration system for automated root filesystem generation. In versions 0.11-rc1 and 0.11, defining ISAR_APT_SNAPSHOT_DATE alone does not set the correct timestamp value for security distribution, leading to missed security updates. This issue has been patched via commit 738bcbb.
Published: 2025-11-19T18:52:42.496Z
Updated: 2025-11-19T20:28:15.251Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.