# What is CVE-2020-28493?

> CVE-2020-28493 is a medium-severity flaw (CVSS 5.3) in Jinja from Palletsprojects, published on 1 February 2021. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 3.5%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2020-28493

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 44 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 5.3 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 3.5% (latest exploit-likelihood forecast)
- **Published:** 1 February 2021
- **Record last updated:** 7 November 2023
- **Main product:** Jinja from Palletsprojects
- **Affected products:** 2

## What is CVE-2020-28493? In plain terms

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can slow it down.

### The official description

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.

### What kind of flaw is it?

- CWE-400: Uncontrolled Resource Consumption

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can slow it down

Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`

## Is CVE-2020-28493 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 3.5%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 3.5%, 3.5%, 3.5%, 3.5%, 3.5%, 3.5%, 3.5%.

### Timeline

- 1 February 2021: Published
- 7 November 2023: Record last updated

### How Precursor Intelligence ranks it

CVE-2020-28493 scores **44 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2020-28493?

The published record lists 2 products. Versions are as published: "before 2.11.3" means every version up to, but not including, 2.11.3.

- [Jinja](https://www.precursorintelligence.com/product/palletsprojects/jinja) by [Palletsprojects](https://www.precursorintelligence.com/vendors/palletsprojects) (Application): before 2.11.3
- [Fedora](https://www.precursorintelligence.com/product/fedoraproject/fedora) by [Fedoraproject](https://www.precursorintelligence.com/vendors/fedoraproject) (Operating system): 33

## How do I fix CVE-2020-28493?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [github.com](https://github.com/pallets/jinja/pull/1343) (Patch, Third-party advisory)
- [github.com](https://github.com/pallets/jinja/blob/ab81fd9c277900c85da0c322a2ff9d68a235b2e6/src/jinja2/utils.py%23L20) (Broken link)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PVAKCOO7VBVUBM3Q6CBBTPBFNP5NDXF4/)
- [security.gentoo.org](https://security.gentoo.org/glsa/202107-19) (Third-party advisory)
- [snyk.io](https://snyk.io/vuln/SNYK-PYTHON-JINJA2-1012994) (Exploit, Third-party advisory)

## Questions

### What is CVE-2020-28493?

CVE-2020-28493 is a medium-severity flaw in Jinja from Palletsprojects, published on 1 February 2021. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can slow it down.

### How serious is CVE-2020-28493?

It scores 5.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2020-28493 is 44 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2020-28493 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 3.5%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2020-28493 affect?

For Jinja from Palletsprojects: before 2.11.3. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2020-28493?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2020-28493 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact