You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gems/avo/CVE-2023-34102.yml
+32-14Lines changed: 32 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ date: 2023-06-06
8
8
description: |
9
9
### Summary
10
10
11
-
"The polymorphic field type stores the classes to operate on when updating
11
+
The polymorphic field type stores the classes to operate on when updating
12
12
a record with user input, and does not validate them in the back end.
13
13
This can lead to unexpected behavior, remote code execution, or
14
14
application crashes when viewing a manipulated record.
@@ -29,20 +29,38 @@ description: |
29
29
30
30
### PoC
31
31
32
-
\n_In the test scenario we choose the demo app and the review resource which has a polymorphic
the request and switching the review[reviewable_type] from “Fish”
35
-
to “File” which is a real class inside Rails_\n_Corrupting
36
-
the database with unusable classes will cause a crash at the
37
-
application while viewing the new record or the index
delete the corrupted resource in order to recover the applications functionality_\n\n\n_Of
40
-
course it is possible to use other class names or namespaces. The
Of course it is possible to use other class names or namespaces. The
41
56
local development environment displays the backend error message
42
57
when visiting a corrupted record. Avo is trying to apply a scope to
43
-
this class that does not exist._\n\n\n_Specifying
44
-
an invalid class name in the parameter will cause the application
45
-
to crash again while trying constanize the provided string_
0 commit comments