CVE-2024-42363: GHSL-2023-136_Samson

Published Aug 20, 2024
·
Updated

Prior to 3385, the user-controlled role parameter enters the application in the Kubernetes::RoleVerificationsController. The role parameter flows into the RoleConfigFile initializer and then into the Kubernetes::Util.parsefile method where it is unsafely deserialized using the YAML.loadstream method. This issue may lead to Remote Code Execution (RCE). This vulnerability is fixed in 3385.

Affected Software

1 affected component
Kubernetes kubernetes<3385

Event History

Aug 20, 2024
CVE Published
via MITRE·08:20 PM
Data Sourced
via MITRE·08:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-42363?

The severity of CVE-2024-42363 is classified as high due to the potential for remote code execution through unsafely deserialized user input.

2

How do I fix CVE-2024-42363?

To fix CVE-2024-42363, update your Kubernetes installation to version 3385 or later.

3

What software is affected by CVE-2024-42363?

CVE-2024-42363 affects Kubernetes versions prior to 3385.

4

What is the impact of CVE-2024-42363?

The impact of CVE-2024-42363 includes potential unauthorized access and manipulation of application data.

5

How does CVE-2024-42363 occur?

CVE-2024-42363 occurs when a user-controlled role parameter is unsafely deserialized in the Kubernetes::RoleVerificationsController.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203