dbcve.org
Portable Runtime UtilityApplication · Apache

CVE-2022-25147

MEDIUM · 6.5 CVSS v3.1 Published 2023-01-31
Fix available
A fix is available. Upgrade to after 1.6.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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_base64 functions of Apache Portable Runtime Utility (APR-util) allows an attacker to write beyond bounds of a buffer. This issue affects Apache Portable Runtime Utility (APR-util) 1.6.1 and prior versions.

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 apr_base64 functions of Apache Portable Runtime Utility (APR-util) allows attackers to write beyond buffer boundaries. The vulnerability occurs in base64 encoding/decoding functions where integer arithmetic wraps around, causing incorrect buffer size calculations that lead to buffer overflows.

MitigationUpgrade to Apache Portable Runtime Utility (APR-util) version 1.6.2 or later which contains the fix for this integer overflow vulnerability in apr_base64 functions.

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 Runtime UtilityApplication
Affected:<= 1.6.1

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 APR-util library location
    Search for libaprutil.so (Linux) or libaprutil.dll (Windows) in system directories, or check bundling in applications using: find /usr -name 'libaprutil*' 2>/dev/null on Linux, or examine application dependencies on Windows with tools like Dependency Walker
    Affected if APR-util library is present in the environment
  2. Determine installed APR-util version
    Run 'apr-util-config --version' if available, or check the library file metadata: 'ls -la libaprutil.so' or examine version resources on Windows. For source installations, check the version.h or configure.ac file in the APR-util source directory
    Affected if Version is 1.6.1 or lower (the vulnerable range)
  3. Identify applications using apr_base64 functions
    Search application binaries or code for calls to apr_base64_encode_len, apr_base64_encode, apr_base64_decode_len, or apr_base64_decode functions. Use 'strings' or 'nm' on binaries, or grep source code for these function names
    Affected if The application actively uses apr_base64 encoding or decoding functions
  4. Verify APR-util is linked dynamically
    Check if vulnerable applications load libaprutil at runtime using 'ldd <application>' on Linux or examine import tables on Windows. Dynamic linking means the system APR-util version applies
    Affected if APR-util is dynamically linked and the system version is <= 1.6.1

You are affected if APR-util version 1.6.1 or lower is installed and any application or service in your environment uses apr_base64 encoding or decoding functions.

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
Upgrade available Upgrade to a release after 1.6.1
Interim mitigation

Upgrade to Apache Portable Runtime Utility (APR-util) version 1.6.2 or later which contains the fix for this integer overflow vulnerability in apr_base64 functions.

Recommended fix High confidence

APR-util 1.6.2

  1. 1. Identify all applications and systems that depend on Apache Portable Runtime Utility (APR-util) version 1.6.1 or earlier.
  2. 2. Locate the APR-util library in your deployment (check application bundling, system libraries, or dependency management configurations).
  3. 3. Obtain APR-util version 1.6.2 or later from the official Apache APR project repository at https://apr.apache.org/.
  4. 4. Replace the vulnerable APR-util library with the new version in all affected locations.
  5. 5. Rebuild or recompile any applications statically linked against the old APR-util library.
  6. 6. Restart all services or applications that use APR-util to load the updated library.
  7. 7. Verify the update was successful by confirming the new APR-util version is loaded (e.g., via application logging or runtime checks).
Caveat Minimal risk - this is a patch release containing security fixes; maintain API/ABI compatibility with 1.6.x branch

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

Fix this in Portable Runtime Utility Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25147 — 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-25147 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