1sealsemantic last-mile verification

Research / Finding

containment-check for targets_base_url in fetch_target

F-AWS-TOUGH-006

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/toughReported fixawslabs/tough

containment-check for targets_base_url in fetch_target

fixed publicly
details
Finding IDs
F-AWS-TOUGH-006
Status
fixed publicly
Reported via
security contact
Note
public code in tough 0.22.0 appears to close this read-side variant even though no separate advisory line was published for it. inferred from public diff 0ba39c5, which adds a containment-check for targets_base_url in fetch_target.

F-AWS-TOUGH-006: File / path escapes. Target retrieval omits the targets_base_url containment check; the write-side CVE mapping is not claimed. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-AWS-TOUGH-006

Security area (1seal assessment): Authorization. Target retrieval omits the targets_base_url containment check; the write-side CVE mapping is not claimed. 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.