Sensitive information disclosure via link identification SSRF
Published Apr 17, 2025 · Updated Apr 21, 2025
Server-side request forgery in Lm21 twonav 2.1.18-20241105 allows remote attackers to read sensitive data via link identification. The public record identifies the link identification function as the request locus but does not disclose the attacker-controlled value or the missing destination validation. Network access requires no privileges or user interaction; the documented consequence is sensitive-data exposure with low integrity impact and no service interruption.
Summary
What happened
Server-side request forgery in Lm21 twonav 2.1.18-20241105 allows remote attackers to read sensitive data via link identification. The public record identifies the link identification function as the request locus but does not disclose the attacker-controlled value or the missing destination validation. Network access requires no privileges or user interaction; the documented consequence is sensitive-data exposure with low integrity impact and no service interruption.
The record
- CVE
- CVE-2025-29449
- Published
- Apr 17, 2025
- Updated
- Apr 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-918, CAPEC-664
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2025CVE publishedPublication date reported by the CVE source.
- Apr 21, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Yuque twonav link-identification proof of conceptproof of concept · unverified
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