CVE-2020-24554
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe redirect module in Liferay Portal before 7.3.3 does not limit the number of URLs resulting in a 404 error that is recorded, which allows remote attackers to perform a denial of service attack by making repeated requests for pages that do not exist.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe redirect module in Lifer Portal before 7.3.3 does not impose a limit on the number of 404 error URLs it records. An attacker can repeatedly request non-existent pages, causing unbounded recording of these URLs and leading to resource exhaustion (database/disk space) and denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Lifer Portal versionAccess the Lifer Portal Control Panel, go to Configuration > System Information, or check the portal.properties file for the version property. Alternatively, examine the portal-impl.jar manifest file or the liferay-portal version file in the installation directory.Affected if The installed version is less than 7.3.3
-
Verify redirect module is enabledCheck the Lifer Portal module registry or osgi console for the redirect module status. Look for com.lifecycle.portal.redirect or similar module name in the OSGi console at /o/system/console/modules.Affected if The redirect module is active and running
-
Inspect 404 redirect recording configurationExamine the redirect module configuration file (redirects.properties or redirect-config.xml in the portal WEB-INF or configuration directory). Look for properties controlling URL recording behavior such as record404Urls, max404Urls, or similar settings.Affected if The module has no limit configured or allows unlimited 404 URL recording (property set to 0 or missing max limit setting)
-
Check database for recorded 404 URLsQuery the Redirect_404 or similar table in the Lifer Portal database. Run a SELECT COUNT(*) on tables related to redirects and 404 logging to see the number of recorded URLs.Affected if There is an unbounded or excessively growing number of recorded 404 URLs in the database
A user is affected if they are running Lifer Portal version prior to 7.3.3 with the redirect module enabled and unlimited 404 URL recording is occurring.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.3.3
Upgrade to Lifer Portal 7.3.3 or later which includes the fix to limit 404 URL recording. Alternatively, implement rate limiting at the web application firewall or load balancer to mitigate the repeated requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24554 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-24554 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data