dbcve.org
Portable RuntimeApplication · Apache

CVE-2022-24963

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Integer Overflow or Wraparound vulnerability in apr_encode functions of Apache Portable Runtime (APR) allows an attacker to write beyond bounds of a buffer. This issue affects Apache Portable Runtime (APR) version 1.7.0.

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 confidence

Integer overflow in the apr_encode functions of Apache Portable Runtime (APR) version 1.7.0 allows an attacker to write beyond the bounds of a buffer due to improper integer arithmetic that wraps around, potentially leading to heap or stack buffer overflows with arbitrary write capabilities.

MitigationUpgrade Apache Portable Runtime to version 1.7.1 or later which contains the patch for this integer overflow vulnerability, and rebuild any applications statically linked against the vulnerable APR library.

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
Portable RuntimeApplication
Affected:= 1.7.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed APR version
    Run 'apr-config --version' or check the libapr library file version (e.g., 'ls -la libapr-*' or 'dpkg -l libapr1' on Debian-based systems)
    Affected if The version returned is exactly 1.7.0
  2. Check application linkage to APR
    Use 'ldd <application_binary>' for dynamic linking or check build artifacts for static linking (look for libapr.a or mention of APR in compile flags)
    Affected if The application links to APR version 1.7.0 either dynamically or statically
  3. Identify if apr_encode functions are used
    Search application code or binary for usage of apr_encode functions: 'grep -r apr_encode /path/to/code' or 'strings <binary> | grep apr_encode'
    Affected if The application or its dependencies use apr_encode, apr_encode_all, or similar encoding functions from APR
  4. Verify encoding input handling
    Review application code that passes user-controlled or network data to apr_encode functions; check for calls with large input lengths that could trigger integer overflow
    Affected if The application passes external input to APR encoding functions without length validation

The environment is affected if APR version 1.7.0 is installed and any application or service uses the apr_encode functions with untrusted or large input data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Portable Runtime to version 1.7.1 or later which contains the patch for this integer overflow vulnerability, and rebuild any applications statically linked against the vulnerable APR library.

Recommended fix Moderate confidence

APR 1.7.2 or later stable release

  1. 1. Identify all systems and applications using Apache Portable Runtime (APR) version 1.7.0
  2. 2. Download or obtain the latest stable release of Apache Portable Runtime (APR) from the official Apache repository (https://apr.apache.org/)
  3. 3. Replace the vulnerable apr_encode functions library (libapr-1.so or apr-1.dll) with the updated version
  4. 4. Rebuild or recompile any applications statically linked against the vulnerable APR 1.7.0 library
  5. 5. Restart all services and applications that use APR to load the updated library
  6. 6. Verify the installed APR version matches the fixed release using 'apr-config --version' or equivalent
Caveat Review release notes for any API/ABI changes between 1.7.0 and the target upgrade version; minor version upgrades typically maintain backward compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Portable Runtime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24963 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24963 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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