How severe is CVE-2013-2254?

No CVSS score has been assigned to CVE-2013-2254 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-2254?

CVE-2013-2254 affects the following packages: org.apache.sling:org.apache.sling.api (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-2254?

Update org.apache.sling:org.apache.sling.api to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2254 is resolved across your whole dependency graph.

How do I detect CVE-2013-2254 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2254 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2013-2254 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-2254, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-2254?

CVE-2013-2254 has an EPSS (Exploit Prediction Scoring System) score of 4.1%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-2254?

CVE-2013-2254 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2013-2254 published, and has it been updated?

CVE-2013-2254 was published on May 17, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2013-2254 — org.apache.sling.api

CVE-2013-2254 is a Buffer Overflow vulnerability in org.apache.sling:org.apache.sling.api. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.sling:org.apache.sling.api — see the affected versions and patch details below.

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

Published

May 17, 2022

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.sling:org.apache.sling.api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.sling:org.apache.sling.api`	all versions	2.4.0`org.apache.sling:org.apache.sling.api:2.4.0`

Affected Products

1 product · 2 configurations

Application

org.apache.sling.servlets.postapache

2 versions

2.2.02.3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The deepGetOrCreateNode function in impl/operations/AbstractCreateOperat…

issues.apache.orgNVDAug 2017

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.sling:org.apache.sling.api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.sling:org.apache.sling.api to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-2254 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-2254 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works