VulnerableCode Package Details - pkg:rpm/redhat/automation-controller@4.6.7-1?arch=el9ap

Search for packages

Vulnerability	Summary	Fixed by
VCID-8vr3-83b4-hqd2 Aliases: CVE-2024-56326 GHSA-q2x7-8rv6-6q7h	Jinja has a sandbox breakout through indirect reference to format method An oversight in how the Jinja sandboxed environment detects calls to `str.format` allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the content of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates. Jinja's sandbox does catch calls to `str.format` and ensures they don't escape the sandbox. However, it's possible to store a reference to a malicious string's `format` method, then pass that to a filter that calls it. No such filters are built-in to Jinja, but could be present through custom filters in an application. After the fix, such indirect calls are also handled by the sandbox.	There are no reported fixed by versions.
VCID-e87q-1j8h-93hh Aliases: BIT-django-2024-56374 CVE-2024-56374 GHSA-qcgg-j2x8-h9g8 PYSEC-2025-1	An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)	There are no reported fixed by versions.
VCID-jyfq-pjwy-n7gg Aliases: CVE-2024-56201 GHSA-gmj6-6f8f-6699	Jinja has a sandbox breakout through malicious filenames A bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used. To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates where the template author can also choose the template filename.	There are no reported fixed by versions.

Vulnerability

Summary

Fixed by

VCID-8vr3-83b4-hqd2
Aliases:
CVE-2024-56326
GHSA-q2x7-8rv6-6q7h

Jinja has a sandbox breakout through indirect reference to format method An oversight in how the Jinja sandboxed environment detects calls to `str.format` allows an attacker that controls the content of a template to execute arbitrary Python code. To exploit the vulnerability, an attacker needs to control the content of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates. Jinja's sandbox does catch calls to `str.format` and ensures they don't escape the sandbox. However, it's possible to store a reference to a malicious string's `format` method, then pass that to a filter that calls it. No such filters are built-in to Jinja, but could be present through custom filters in an application. After the fix, such indirect calls are also handled by the sandbox.

There are no reported fixed by versions.

VCID-e87q-1j8h-93hh
Aliases:
BIT-django-2024-56374
CVE-2024-56374
GHSA-qcgg-j2x8-h9g8
PYSEC-2025-1

An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)

There are no reported fixed by versions.

VCID-jyfq-pjwy-n7gg
Aliases:
CVE-2024-56201
GHSA-gmj6-6f8f-6699

Jinja has a sandbox breakout through malicious filenames A bug in the Jinja compiler allows an attacker that controls both the content and filename of a template to execute arbitrary Python code, regardless of if Jinja's sandbox is used. To exploit the vulnerability, an attacker needs to control both the filename and the contents of a template. Whether that is the case depends on the type of application using Jinja. This vulnerability impacts users of applications which execute untrusted templates where the template author can also choose the template filename.

There are no reported fixed by versions.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-01T13:43:34.556886+00:00	RedHat Importer	Affected by	VCID-jyfq-pjwy-n7gg	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2024-56201.json	38.0.0
2026-04-01T13:43:33.374385+00:00	RedHat Importer	Affected by	VCID-8vr3-83b4-hqd2	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2024-56326.json	38.0.0
2026-04-01T13:43:14.199264+00:00	RedHat Importer	Affected by	VCID-e87q-1j8h-93hh	https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2024-56374.json	38.0.0