CVE-2023-34102 is a high-severity improper input validation vulnerability in avo (rubygems), affecting versions <= 2.33.2. It is fixed in 2.33.3.
Summary The polymorphic field type stores the classes to operate on when updating a record with user input, and does not validate them in the back end. This can lead to unexpected behavior, remote code execution, or application crashes when viewing a manipulated record. Details After reviewing the polymorphic field implementation and performing some black box approaches, we identified a potential security issue related to the use of safeconstantize / constantize. This Rails functionality is capable of searching for classes within the Rails context and returning the class for further use. Because Avo does not validate user input when updating or creating a new polymorphic resource, it is possible to create database entries with completely different or invalid class names than the preselected ones. Avo assumes that the class specified by the user request is a valid one and attempts to work with it, which may result in dangerous behavior and code execution. PoC In the test scenario we choose the demo app and the review resource which has a polymorphic reviewable field. Intercepting the request and switching the review[reviewabletype] from “Fish” to “File” which is a real class inside Rails Corrupting the database with unusable classes will cause a crash at the application while viewing the new record or the index view (partial DoS) Manual delete the corrupted resource in order to recover the applications functionality Of course it is possible to use other class names or namespaces. The local development environment displays the backend error message when visiting a corrupted record. Avo is trying to apply a scope to this class that does not exist. Specifying an invalid class name in the parameter will cause the application to crash again while trying constanize the provided string Impact The final exploitation of this vulnerability requires more time than is provided in this assessment, but initial testing of the post request shows the potential critical risk. The classes could be instantiated at any point in the code and this could also lead to code execution. Recommendation Avo should be configured to never trust user-supplied input, especially when defining classes for records. In this particular case, Avo can evaluate the options list given for the polymorphic field and only allow strings from that list. With this white-list approach, an attacker cannot supply unintended classes.
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2023-34102 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (2.33.3). Upgrading removes the vulnerable code path.
rubygems
avo (<= 2.33.2)avo (>= 3.0.0.pre1, <= 3.0.0.pre12)avo → 2.33.3 (rubygems)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's Application Detection and Response identifies whether CVE-2023-34102 is reachable in your applications. Explore runtime application protection for your team.
See if CVE-2023-34102 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2023-34102 in your environment →Upgrade avo to 2.33.3 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2023-34102 is a high-severity improper input validation vulnerability in avo (rubygems), affecting versions <= 2.33.2. It is fixed in 2.33.3. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
CVE-2023-34102 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
avo (rubygems) versions <= 2.33.2 is affected.
Yes. CVE-2023-34102 is fixed in 2.33.3. Upgrade to this version or later.
Whether CVE-2023-34102 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade avo to 2.33.3 or later.