Authenticated operation bypass via weak MN token validation
Published Dec 21, 2024 · Updated Nov 3, 2025
Authentication bypass in IBM operating system releases 7.3, 7.4, and 7.5 allows remote authenticated users to perform unauthorized Navigator operations. Navigator's doFilter check accepts tampered MN security tokens when final digits are incremented or replaced with zeros rather than rejecting the modified value. A valid Navigator session and associated 19-digit MN token are required, and the bypass grants operations blocked for the account.
Summary
What happened
Authentication bypass in IBM operating system releases 7.3, 7.4, and 7.5 allows remote authenticated users to perform unauthorized Navigator operations. Navigator's doFilter check accepts tampered MN security tokens when final digits are incremented or replaced with zeros rather than rejecting the modified value. A valid Navigator session and associated 19-digit MN token are required, and the bypass grants operations blocked for the account.
The record
- CVE
- CVE-2024-51464
- Published
- Dec 21, 2024
- Updated
- Nov 3, 2025
- Vendor
- IBM
- Product
- IBM i
- Classifications
- CWE-288, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 21, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=7.3, 7.4, 7.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- MN token manipulation proof of conceptproof of concept · demonstrated
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