Memory corruption via unterminated trigram tables
Published Mar 23, 2025 · Updated Mar 24, 2025
Memory corruption in Nintendo's three Animal Crossing GameCube titles at 1.00 and 1.01 allows physically proximate attackers to corrupt memory. The letter-scoring check B expects 0x7F terminators, but its trigram tables end in 0x00, so unmatched pairs cause reads thousands of bytes beyond each array. Triggering requires an in-game letter containing an unmatched trigram and physical console access; public analysis observes incorrect scoring without a crash or proven code execution.
Summary
What happened
Memory corruption in Nintendo's three Animal Crossing GameCube titles at 1.00 and 1.01 allows physically proximate attackers to corrupt memory. The letter-scoring check B expects 0x7F terminators, but its trigram tables end in 0x00, so unmatched pairs cause reads thousands of bytes beyond each array. Triggering requires an in-game letter containing an unmatched trigram and physical console access; public analysis observes incorrect scoring without a crash or proven code execution.
The record
- CVE
- CVE-2018-25109
- Published
- Mar 23, 2025
- Updated
- Mar 24, 2025
- Vendor
- Nintendo
- Product
- Doubutsu no Mori+
- Classifications
- CWE-119
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.00
- Affected versionversion=1.01
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo