Sensitive-data disclosure via shared ObjectMapper reconfiguration
Published Apr 23, 2021 · Updated Sep 16, 2024
Information disclosure in Vaadin Flow Server 3.0.0 through 3.0.5 allows remote authenticated users to read private object fields. Vaadin Connect reconfigures Spring's shared default ObjectMapper to serialize private and protected properties instead of limiting that change to its own mapper. Exposure requires affected Vaadin 15.0.0 through 15.0.4 with Spring functionality such as @RestController that serializes sensitive fields; the consequence is read-only disclosure.
Summary
What happened
Information disclosure in Vaadin Flow Server 3.0.0 through 3.0.5 allows remote authenticated users to read private object fields. Vaadin Connect reconfigures Spring's shared default ObjectMapper to serialize private and protected properties instead of limiting that change to its own mapper. Exposure requires affected Vaadin 15.0.0 through 15.0.4 with Spring functionality such as @RestController that serializes sensitive fields; the consequence is read-only disclosure.
The record
- CVE
- CVE-2020-36319
- Published
- Apr 23, 2021
- Updated
- Sep 16, 2024
- Vendor
- Vaadin
- Product
- Flow Server
- Classifications
- CWE-200, CWE-668
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 23, 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=3.0.0 <*
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
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