CVE-2021-33321: Liferay Portal and Liferay DXP insecure default configuration

Quick answers

Is CVE-2021-33321 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2021-33321 being exploited in the wild.

How severe is CVE-2021-33321?

Low severity, with a CVSS score of 3.1, published 24 May 2022.

Which products and versions are affected?

com.liferay.portal:com.liferay.portal.impl (Maven) ECOSYSTEM:introduced=0,fixed=5.11.0; com.liferay.portal:release.portal.bom (Maven) ECOSYSTEM:introduced=0,fixed=7.3.3.

Is there a fix for CVE-2021-33321?

Yes. com.liferay.portal:com.liferay.portal.impl (Maven): upgrade to 5.11.0 or later; com.liferay.portal:release.portal.bom (Maven): upgrade to 7.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2021-33321?

Check whether you run com.liferay.portal:com.liferay.portal.impl (Maven) or com.liferay.portal:release.portal.bom (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• com.liferay.portal:com.liferay.portal.impl (Maven): upgrade to 5.11.0 or later

  # set com.liferay.portal:com.liferay.portal.impl to 5.11.0 in your pom.xml or build.gradle

• com.liferay.portal:release.portal.bom (Maven): upgrade to 7.3.3 or later

  # set com.liferay.portal:release.portal.bom to 7.3.3 in your pom.xml or build.gradle

Affected products

• com.liferay.portal:com.liferay.portal.impl (Maven) ECOSYSTEM:introduced=0,fixed=5.11.0
• com.liferay.portal:release.portal.bom (Maven) ECOSYSTEM:introduced=0,fixed=7.3.3

Identifiers

• CVE-2021-33321
• GHSA-jfch-m2x3-2v66