Portable RuntimeApplication · Apache
CVE-2022-28331
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 · uneditedOn Windows, Apache Portable Runtime 1.7.0 and earlier may write beyond the end of a stack based buffer in apr_socket_sendv(). This is a result of integer overflow.
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 confidenceApache Portable Runtime 1.7.0 and earlier on Windows contains an integer overflow vulnerability in the apr_socket_sendv() function that allows writing beyond the bounds of a stack-based buffer, potentially leading to remote code execution.
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
<= 1.7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the APR library file on WindowsSearch for apr.dll or libapr-1.dll in system directories (C:\Windows\System32), application installation folders, or use 'dir /s /b apr*.dll' from drive root to find all copiesAffected if APR library file exists on the Windows system
-
Determine the installed APR versionRight-click the apr.dll or libapr-1.dll file, select Properties, then go to the Details tab to view File Version; alternatively, use PowerShell: (Get-Item 'path\to\apr.dll').VersionInfoAffected if The version shown is 1.7.0 or earlier, or if no version information is displayed and the file was created before the 1.7.1 patch date
-
Verify the Windows platformConfirm the operating system is Windows (any version); this vulnerability only affects Windows implementations of APRAffected if Running on Windows and APR is present
-
Check for applications using apr_socket_sendvReview application code or dependencies to determine if they call the apr_socket_sendv() function; this function is the vulnerable entry pointAffected if An application linked against the vulnerable APR library calls apr_socket_sendv()
A user is affected if they have Apache Portable Runtime version 1.7.0 or earlier installed on a Windows system, and an application uses the apr_socket_sendv() function.
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 · scopedUpgrade Apache Portable Runtime to version 1.7.1 or later on all affected Windows systems. Identify and remediate any applications that depend on the vulnerable APR library.
Apache Portable Runtime 1.7.1 or later
- Identify all applications and services that depend on Apache Portable Runtime (APR) <= 1.7.0 on Windows systems
- Locate the APR library files (typically apr-1.dll or libapr-1.so depending on platform, though this specific issue is Windows-only)
- Obtain Apache Portable Runtime version 1.7.1 or later from the official Apache APR distribution (https://apr.apache.org/)
- Replace the existing APR library files with the updated version 1.7.1+
- Restart any dependent services (such as Apache HTTP Server) that load the APR library
- Verify the updated version by checking apr-version.h or using any version-checking utility provided by the application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Portable Runtime
Scoped from the published advisory
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28331 — 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-2022-28331 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