This affects the package jinja2 from 0.0.0 and before 2.11.3. The ReDoS vulnerability is mainly due to the _punctuation_re regex
operator and its use of multiple wildcards. The last wildcard is the most exploitable as it searches for trailing punctuation. This issue can be mitigated by Markdown to format user content instead of the urlize filter, or by implementing request timeouts and limiting process memory.
The product does not properly control the allocation and maintenance of a limited resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Jinja | Palletsprojects | * | 2.11.3 (excluding) |
Red Hat Enterprise Linux 8 | RedHat | python27:2.7-8050020210811095446.3e7ace8b | * |
Red Hat Enterprise Linux 8 | RedHat | python-jinja2-0:2.10.1-3.el8 | * |
Red Hat Enterprise Linux 8 | RedHat | python38:3.8-8050020210811101222.e3d35cca | * |
Red Hat Enterprise Linux 8 | RedHat | python38-devel:3.8-8050020210811101222.e3d35cca | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | python27-babel-0:0.9.6-10.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | python27-python-0:2.7.18-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | python27-python-jinja2-0:2.6-16.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | python27-python-pygments-0:1.5-5.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-babel-0:2.7.0-12.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-0:3.8.11-2.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-cryptography-0:2.8-5.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-jinja2-0:2.10.3-6.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-lxml-0:4.4.1-7.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-pip-0:19.3.1-2.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-python38-python-urllib3-0:1.25.7-7.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | python27-babel-0:0.9.6-10.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | python27-python-0:2.7.18-3.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | python27-python-jinja2-0:2.6-16.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | python27-python-pygments-0:1.5-5.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-babel-0:2.7.0-12.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-0:3.8.11-2.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-cryptography-0:2.8-5.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-jinja2-0:2.10.3-6.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-lxml-0:4.4.1-7.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-pip-0:19.3.1-2.el7 | * |
Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS | RedHat | rh-python38-python-urllib3-0:1.25.7-7.el7 | * |
Jinja2 | Ubuntu | bionic | * |
Jinja2 | Ubuntu | esm-infra-legacy/trusty | * |
Jinja2 | Ubuntu | esm-infra/bionic | * |
Jinja2 | Ubuntu | esm-infra/focal | * |
Jinja2 | Ubuntu | esm-infra/xenial | * |
Jinja2 | Ubuntu | focal | * |
Jinja2 | Ubuntu | groovy | * |
Jinja2 | Ubuntu | hirsute | * |
Jinja2 | Ubuntu | impish | * |
Jinja2 | Ubuntu | precise/esm | * |
Jinja2 | Ubuntu | trusty | * |
Jinja2 | Ubuntu | trusty/esm | * |
Jinja2 | Ubuntu | upstream | * |
Jinja2 | Ubuntu | xenial | * |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.