GHSA-hj3g-hh5f-63mp: Discovery peer contact book poisoning via future timestamps

Discovery peer contact book poisoning via future timestamps

F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

GHSA-hj3g-hh5f-63mpGHSAnimiq/core-rs-albatross

Discovery peer contact book poisoning via future timestamps

Fixed in: v1.3.0

patched

details

Finding IDs: F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001
GHSA: GHSA-hj3g-hh5f-63mp
Status: patched
Fixed in: v1.3.0
Recorded credit: finder: @1seal
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
Upstream title: Discovery peer contact book poisoning via future timestamps
Upstream CWE: CWE-345, CWE-1284
Upstream publication: 22 Apr 2026
Upstream updated: 22 Apr 2026
Metadata fetched: 23 Sep 2026
Upstream @1seal credit: @1seal: finder (accepted)

F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001: Input / state handling. Discovery timestamps lack the required future-time range check. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001

Security area (1seal assessment): Integrity. Unchecked future timestamps can poison the peer contact book, compromising the integrity of stored discovery state. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.