CVE-2024-55636: Drupal core contains a potential PHP Object Injection vulnerability

Published Dec 9, 2024
·
Updated

Deserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.

Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so called gadget chain presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.

Other sources

Drupal core contains a potential PHP Object Injection vulnerability

— Packagist

Affected Software

21 affected componentsFixes available
Drupal Drupal>=8.0.0<10.2.11
Drupal Drupal>=10.3.0<10.3.9
Drupal Drupal>=11.0.0<11.0.8
composer/drupal/drupal>=11.0.0<11.0.8
11.0.8
composer/drupal/drupal>=10.3.0<10.3.9
10.3.9
composer/drupal/drupal>=8.8.0<10.2.11
10.2.11
composer/drupal/core-recommended>=11.0.0<11.0.8
11.0.8
composer/drupal/core-recommended>=10.3.0<10.3.9
10.3.9
composer/drupal/core-recommended>=8.8.0<10.2.11
10.2.11
composer/drupal/core>=11.0.0<11.0.8
11.0.8
composer/drupal/core>=10.3.0<10.3.9
10.3.9
composer/drupal/core>=8.8.0<10.2.11
10.2.11
composer/drupal/core>=11.0.0, <11.0.8
11.0.8
composer/drupal/core>=10.3.0, <10.3.9
10.3.9
composer/drupal/core>=8.8.0, <10.2.11
10.2.11
composer/drupal/core-recommended>=11.0.0, <11.0.8
11.0.8
composer/drupal/core-recommended>=10.3.0, <10.3.9
10.3.9
composer/drupal/core-recommended>=8.8.0, <10.2.11
10.2.11
composer/drupal/drupal>=11.0.0, <11.0.8
11.0.8
composer/drupal/drupal>=10.3.0, <10.3.9
10.3.9
composer/drupal/drupal>=8.8.0, <10.2.11
10.2.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 11.0.8
  2. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 10.3.9
  3. Upgrade

    Upgrade composer/drupal/drupal to a version that resolves this vulnerability.

    Fixed in 10.2.11
  4. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 11.0.8
  5. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 10.3.9
  6. Upgrade

    Upgrade composer/drupal/core-recommended to a version that resolves this vulnerability.

    Fixed in 10.2.11
  7. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 11.0.8
  8. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 10.3.9
  9. Upgrade

    Upgrade composer/drupal/core to a version that resolves this vulnerability.

    Fixed in 10.2.11
  10. Upgrade

    Upgrade Drupal Core to a version that resolves this vulnerability.

    Patch SA-CORE-2024-006

Event History

Dec 9, 2024
CVE Published
via MITRE·11:24 PM
Data Sourced
via MITRE·11:24 PM
DescriptionWeakness
Dec 10, 2024
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:31 AM
Data Sourced
via GitHub·12:31 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Packagist·12:31 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-55636?

CVE-2024-55636 is a critical severity vulnerability that allows for object injection through deserialization of untrusted data in Drupal Core.

2

How do I fix CVE-2024-55636?

To fix CVE-2024-55636, you should update Drupal Core to versions 11.0.8, 10.3.9, or 10.2.11, depending on your currently installed version.

3

Which versions of Drupal are affected by CVE-2024-55636?

CVE-2024-55636 affects Drupal Core versions prior to 10.2.11, 10.3.9, and 11.0.8.

4

Is CVE-2024-55636 easy to exploit?

Yes, the vulnerability can be easily exploited by attackers due to unsafe deserialization handling.

5

What can happen if I don't remediate CVE-2024-55636?

If CVE-2024-55636 is not remediated, it can allow attackers to execute arbitrary code or modify site data through object injection.

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