Mareforma: transparency_logged trusts the unsigned rekor block
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mareforma | mareforma | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mareforma | Mareforma |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-xfq4-8hf9-5h43 | Mareforma: transparency_logged trusts the unsigned rekor block |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.083% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mareforma
Mareforma mareforma |
|
| Vendors & Products |
Mareforma
Mareforma mareforma |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, restore logic in mareforma/db/restore.py derives transparency_logged from the unsigned rekor.uuid field inside signature_bundle without requiring a verified claim-bound rekor_inclusions entry, so an attacker who modifies claims.toml can falsely make a claim eligible for REPLICATED convergence. The same logic resets signed claims in non-Rekor graphs from transparency_logged 1 to 0 after restore, permanently preventing convergence because no Rekor refresh is configured. This issue is fixed in version 0.3.8. | |
| Title | Mareforma: transparency_logged trusts the unsigned rekor block | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV4_0
|