Client-side object pollution via recursive URL merge
Published Jul 21, 2021 · Updated Sep 16, 2024
Prototype pollution in GraphHopper web bundle before 3.2 and 4.0 prereleases allows remote attackers to alter client-side object behavior. The mergeParamIntoObject function recursively follows dot-separated URL keys without rejecting proto, constructor, or prototype segments. Exploitation requires a victim to open a crafted GraphHopper Maps URL; the polluted prototype can change or interrupt behavior in that browser session.
Summary
What happened
Prototype pollution in GraphHopper web bundle before 3.2 and 4.0 prereleases allows remote attackers to alter client-side object behavior. The mergeParamIntoObject function recursively follows dot-separated URL keys without rejecting proto, constructor, or prototype segments. Exploitation requires a victim to open a crafted GraphHopper Maps URL; the polluted prototype can change or interrupt behavior in that browser session.
The record
- CVE
- CVE-2021-23408
- Published
- Jul 21, 2021
- Updated
- Sep 16, 2024
- Vendor
- GraphHopper
- Product
- GraphHopper
- Classifications
- CWE-1321, CAPEC-1, CAPEC-180, CAPEC-77, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record 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=4.0-pre1 <unspecified
- Affected versionversion=unspecified <3.2
- Affected versionversion=unspecified <4.0
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
- Snyk crafted GraphHopper Maps URL 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