Skip to content

Commit f2ea3b9

Browse files
owen-mcCopilot
andauthored
Do not make such a strong security claim
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
1 parent 427b73e commit f2ea3b9

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

java/ql/src/Security/CWE/CWE-502/UnsafeDeserialization.qhelp

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,11 @@ Jackson, Jabsorb, Jodd JSON, Flexjson, Gson, JMS, and Java IO serialization thro
2121
<p>
2222
Note that a deserialization method is only dangerous if it can instantiate
2323
arbitrary classes. Serialization frameworks that use a schema to instantiate
24-
only expected, predefined types are generally safe and are not tracked by this
25-
query. For example, Apache Avro's deserialization methods follow a schema and
26-
therefore cannot instantiate arbitrary classes, making them safe to use even
27-
with untrusted data.
24+
only expected, predefined types are generally not tracked by this query. For
25+
example, Apache Avro's deserialization methods follow a schema and are
26+
therefore generally safe with respect to arbitrary-class-instantiation and
27+
gadget-chain attacks when the schema is trusted and does not permit
28+
user-controlled type resolution.
2829
</p>
2930
</overview>
3031

0 commit comments

Comments
 (0)