CVE-2020-5408: Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0

This month

MEDIUM 6.5UPGRADEUPGRADE

CVE-2020-5408 is a medium-severity flaw (CVSS 6.5) affecting spring security, spring security. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text encryptor. A malicious user with access to the data that has been encrypted using such an encryptor may be able to derive the unencrypted values using a dictionary attack.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-329, CWE-330
Published	2020-05-14
Last modified	2026-06-17

Publisher (CNA): Pivotal Software, Inc. · Vendor: pivotal software · vmware

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-05-14 18:15 UTCPublished CVE record published
2026-06-17 03:21 UTCUpdated Record last modified

pivotal software spring security UPGRADE

Affected: >= 5.2.0 and < 5.2.4 · >= 5.3.0 and < 5.3.2

Fixed in: 5.2.4, 5.3.2

Safe to downgrade to: a release before 5.2.0

1. Check installed version

apt-cache policy spring-security || rpm -q spring-security || spring-security --version

2. UPGRADE to 5.2.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-security

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-security

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.2.0 (Debian / Ubuntu)

apt-cache madison spring-security sudo apt install spring-security=<VERSION_BEFORE_5.2.0> sudo apt-mark hold spring-security

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-security sudo dnf downgrade spring-security-<VERSION_BEFORE_5.2.0> sudo dnf versionlock add spring-security

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

vmware spring security UPGRADE

Affected: >= 4.2.0 and < 4.2.16 · >= 5.0.0 and < 5.0.16 · >= 5.1.0 and < 5.1.10

Fixed in: 4.2.16, 5.0.16, 5.1.10

Safe to downgrade to: a release before 4.2.0

1. Check installed version

apt-cache policy spring-security || rpm -q spring-security || spring-security --version

2. UPGRADE to 4.2.16 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-security

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-security

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.2.0 (Debian / Ubuntu)

apt-cache madison spring-security sudo apt install spring-security=<VERSION_BEFORE_4.2.0> sudo apt-mark hold spring-security

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-security sudo dnf downgrade spring-security-<VERSION_BEFORE_4.2.0> sudo dnf versionlock add spring-security

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-5408?

spring security: upgrade to 5.2.4, 5.3.2; spring security: upgrade to 4.2.16, 5.0.16, 5.1.10. Exact commands for each OS are on this page.

Is CVE-2020-5408 being exploited?

CVE-2020-5408 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-5408 affect?

CVE-2020-5408 affects spring security, spring security. Severity is medium (CVSS 6.5). Spring Security versions 5.3.x prior to 5.3.2, 5.2.x prior to 5.2.4, 5.1.x prior to 5.1.10, 5.0.x prior to 5.0.16 and 4.2.x prior to 4.2.16 use a fixed null initialization vector with CBC Mode in the implementation of the queryable text enc

How urgent is CVE-2020-5408?

Priority 42/100. No elevated risk signals yet.

Software pages

VMware vulnerabilities

Related CVEs

CVE-2026-22754 HIGH 7.5 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22753 HIGH 7.5 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22747 MEDIUM 6.8 UPGRADE Vulnerability in Spring Spring Security. SubjectX500PrincipalExtractor does not correctly handle certain malfo
CVE-2026-22746 LOW 3.7 UPGRADE Vulnerability in Spring Spring Security
CVE-2026-22751 MEDIUM 4.8 UPGRADE Vulnerability in Spring Spring Security

References

← Back to latest CVEs