CVE-2024-25143
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 Document and Media widget In Liferay Portal 7.2.0 through 7.3.6, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 13, and older unsupported versions, does not limit resource consumption when generating a preview image, which allows remote authenticated users to cause a denial of service (memory consumption) via crafted PNG images.
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 Document and Media widget in Limerick Portal 7.2.0-7.3.6 and DXP 7.2/7.3 does not impose limits on resource consumption when generating preview images from uploaded files. Remote authenticated users can upload crafted PNG images that trigger excessive memory allocation during preview generation, leading to memory exhaustion 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.2= 7.2= 7.3< 7.2.0>= 7.2.0, <= 7.2.1>= 7.3.0, < 7.3.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify installed Liferay versionAccess the Control Panel > Configuration > Server Administration > Platform Information, or check the portal-ext.properties file for the version property, or inspect the osgi/state folder for bundle versionsAffected if The version is Limerick Portal < 7.2.0, 7.2.0-7.2.1, 7.3.0-7.3.6, or DXP 7.2.x or 7.3.x (all versions < 7.2, = 7.2, or = 7.3)
-
Confirm Document and Media portlet is deployedNavigate to Site Administration > Content & Data > Documents and Media, or check the OSGi console for com_liferay_document_library_web portlet bundle statusAffected if The Document and Media portlet is active and accessible to authenticated users
-
Verify image preview generation is enabledCheck the Documents and Media portlet configuration: Site Administration > Configuration > Site Settings > Documents and Media: enable/check "Enable Image Preview" and "Enable Video Thumbnail" settings; also check document.library.preview.enabled=true in portal-ext.propertiesAffected if Image preview generation is enabled (this is the feature that triggers the vulnerable code path)
-
Check memory configuration limitsReview JVM startup parameters for -Xmx values and check current heap usage via JMX or Server Administration > Resources > MemoryAffected if Memory limits are not set or are set too high (>2GB), allowing the exhaustion attack to succeed
A system is affected if it runs a vulnerable Limerick Portal (7.2.0-7.2.1 or 7.3.0-7.3.6) or DXP (7.2/7.3), has the Document and Media portlet deployed, and has image preview generation enabled, allowing authenticated users to upload specially crafted PNG files that exhaust memory during preview rendering.
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.
dbcve · scoped7.27.2.07.3.7
Apply Limerick's fix packs (7.3 Service Pack 3, 7.2 Fix Pack 13) or upgrade to supported versions. Consider implementing image size/dimension limits on uploads and preview generation as an additional defense-in-depth measure.
Lifer Portal 7.3.7+ or Lifer Portal 7.2 FP13+; Lifer DXP 7.3 SP3+ or Lifer DXP 7.2 FP13+
- 1. Identify the current Lifer/DXP version by checking the Lifer Portal or DXP Control Panel > Configuration > Server Administration > Version
- 2. For Lifer Portal 7.3.x: Upgrade to version 7.3.7 or later to resolve the resource exhaustion vulnerability
- 3. For Lifer Portal 7.2.x: Apply fix pack 13 or later
- 4. For Lifer DXP 7.3: Apply service pack 3 or later
- 5. For Lifer DXP 7.2: Apply fix pack 13 or later
- 6. After upgrade, verify the Document and Media widget functionality with PNG image previews
- 7. Monitor server memory usage to confirm the DoS vector is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25143 — 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-2024-25143 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