Improper Restriction of Operations within the Bounds of a Memory Buffer in Apache Sling

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2013-2254: 4.09% estimated exploitation activity in the next 30 days; percentile 90.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The deepGetOrCreateNode function in impl/operations/AbstractCreateOperation.java in org.apache.sling.servlets.post.bundle 2.2.0 and 2.3.0 in Apache Sling does not properly handle a NULL value that returned when the session does not have permissions to the root node, which allows remote attackers to cause a denial of service (infinite loop) via unspecified vectors.

Published by the source

17 May 2022, 01:36 UTC

Last modified by the source

27 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:53 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cxwh-vmhg-39r2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-2254

Advisory: Improper Restriction of Operations within the Bounds of a Memory Buffer in Apache Sling
IDs: CVE-2013-2254, GHSA-cxwh-vmhg-39r2
Record: https://patchnext.com/advisories/cve-2013-2254 (revision 1, source checked 26 Oct 2026, 15:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.sling:org.apache.sling.api 2.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.sling:org.apache.sling.api: affected <= 2.3.0; fixed in 2.4.0

## Suggested inspection (read-only)
- Maven org.apache.sling:org.apache.sling.api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.sling:org.apache.sling.api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cxwh-vmhg-39r2 (GitHub-reviewed advisory GHSA-cxwh-vmhg-39r2 lists affected ranges: Maven org.apache.sling:org.apache.sling.api >=0 <=2.3.0)

Commands are suggestions: review each one before running it.