SUSE-SU-2024:2616-1 Security update for python-Django
Not scored
Published
Check this codebase for SUSE-SU-2024:2616-1 and fix it if it is affected.
What it is: SUSE-SU-2024:2616-1 is a vulnerability in python-Django, published on 29 Jul 2024.
Exploitation: There is no known exploitation of SUSE-SU-2024:2616-1 in the wild and no public exploit code.
Affected product: python-Django. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2024-2616-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2024-2616-1/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is SUSE-SU-2024:2616-1?
SUSE-SU-2024:2616-1 is a vulnerability in python-Django, published on 29 Jul 2024.
Official description
This update for python-Django fixes the following issues:
- Fixed regression in previous CVE fixes that made the package not work with Python 3.6
Which versions are affected by SUSE-SU-2024:2616-1?
Linux distribution packages (1)
python-Django openSUSE:Leap 15.5 | All versions | 2.0.7-150000.1.23.1 |
How do I fix SUSE-SU-2024:2616-1?
Upgrade to a fixed version.
Is SUSE-SU-2024:2616-1 being exploited?
There is no known exploitation of SUSE-SU-2024:2616-1 in the wild and no public exploit code.