Class Pollution Affecting django-unicorn package, versions [,0.62.0)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-DJANGOUNICORN-8685541
- published4 Feb 2025
- disclosed3 Feb 2025
- creditsuperboy-zjc, jackfromeast
Introduced: 3 Feb 2025
CVE-2025-24370 (opens in a new tab)How to fix?
Upgrade django-unicorn to version 0.62.0 or higher.
Overview
django-unicorn is an A magical full-stack framework for Django.
Affected versions of this package are vulnerable to Class Pollution in the set_property_value() function. An attacker can manipulate the Python runtime environment and trigger unintended behaviors by providing malicious values in a component request. The property_name parameter accepts directory-traversing pathname values, which the attacker can use to point to an arbitrary location in the Python runtime, and the property_value can hold an arbitrary malicious value, including a global (__/dunder) property.
Several kinds of undesirable impact have been demonstrated based on the manipulation of other modules by polluting their dependency paths in this way. Impacts include cross-site scripting, denial of service and authentication bypass by overwriting a secret key.