Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
adamant-im/adamant-ios
develop @ 7823857
6
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Cryptographic Address Validation Bypass: 3 prior fixes. Scrutinize any change in this area.
Adamant/Stories/Account/TransferViewController.swift: most-fixed (2 issues). Treat as high-risk during review.
2 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Cryptographic Address Validation Bypass: Inconsistent or transposed address validation rules (specifically Ethereum vs. ADAMANT formats) and a lack of explicit validation enforcement prior to completing transactions can result in funds being transferred to invalid or unexpected destinations.
Cryptographic Issues: Deviations in key derivation mechanisms, such as using incorrect hash variants (SHA-512 instead of SHA-256) or misinterpreting passphrase formats as hex-decoded instead of raw bytes, compromise wallet security and lead to incompatible key derivation.
Auth Bypass: Operating push token registration or unregistration services without validating that an active user account is authenticated can leak account activities or allow unauthorized modifications.