CVE-2018-20301: Input Validation
First published: Thu Dec 20 2018(Updated: )
An issue was discovered in Steve Pallen Coherence before 0.5.2 that is similar to a Mass Assignment vulnerability. In particular, "registration" endpoints (e.g., creating, editing, updating) allow users to update any coherence_fields data. For example, users can automatically confirm their accounts by sending the confirmed_at parameter with their registration request.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Coherence | <0.5.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-20301?
CVE-2018-20301 is classified as a medium severity vulnerability due to its potential impact on user account security.
How do I fix CVE-2018-20301?
To fix CVE-2018-20301, upgrade to version 0.5.2 or later of the Coherence software to eliminate the mass assignment vulnerability.
What types of systems are affected by CVE-2018-20301?
CVE-2018-20301 affects all versions of the Coherence software prior to 0.5.2, allowing unauthorized changes to coherence_fields.
What can attackers do with CVE-2018-20301?
Attackers can exploit CVE-2018-20301 to manipulate or update coherence_fields data, potentially confirming accounts without authorization.
Is CVE-2018-20301 still a risk for users?
If users are still running versions of Coherence before 0.5.2, they remain at risk for exploitation through CVE-2018-20301.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/severity
- agent/weakness
- agent/first-publish-date
- agent/description
- agent/last-modified-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/coherence project
- canonical/oracle coherence