Improper handling of REST API XML deserialization errors in Jenkins
High severity
GitHub Reviewed
Published
May 24, 2022
to the GitHub Advisory Database
•
Updated Dec 14, 2023
Package
Affected versions
<= 2.263.1
>= 2.264, <= 2.274
Patched versions
2.263.2
2.275
Description
Published by the National Vulnerability Database
Jan 13, 2021
Published to the GitHub Advisory Database
May 24, 2022
Reviewed
Jun 23, 2022
Last updated
Dec 14, 2023
Jenkins provides XML REST APIs to configure views, jobs, and other items. When deserialization fails because of invalid data, Jenkins 2.274 and earlier, LTS 2.263.1 and earlier stores invalid object references created through these endpoints in the Old Data Monitor. If an administrator discards the old data, some erroneous data submitted to these endpoints may be persisted.
This allows attackers with View/Create, Job/Create, Agent/Create, or their respective */Configure permissions to inject crafted content into Old Data Monitor that results in the instantiation of potentially unsafe objects when discarded by an administrator.\n\nJenkins 2.275, LTS 2.263.2 does not record submissions from users in Old Data Monitor anymore.
In case of problems, the Java system properties
hudson.util.RobustReflectionConverter.recordFailuresForAdmins
andhudson.util.RobustReflectionConverter.recordFailuresForAllAuthentications
can be set to true to record configuration data submissions from administrators or all users, partially or completely disabling this fix.References