1sealsemantic last-mile verification

Research / Finding

Fast-fail on incorrect MaxSpanID

F-SOCI-OOB-001

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

Read the evidence · View in research browse

Recorded evidence

—score not recorded
awslabs/soci-snapshotterReported fixawslabs/soci-snapshotter

Fast-fail on incorrect MaxSpanID

fixed publicly
details
Finding IDs
F-SOCI-OOB-001
Status
fixed publicly
Reported via
security contact
Note
fixed by #1916, merged 2026-04-01, merge commit 0a1984bb2ffb. AWS said it was still determining whether a GHSA would be published.

F-SOCI-OOB-001: Memory safety. Span/checkpoint count mismatch permits a C heap out-of-bounds read. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-SOCI-OOB-001

Security area (1seal assessment): Memory safety. The span manager validates MaxSpanID against checkpoint and digest counts before indexing span data. Reviewed 21 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.