dbcve.org
Libapreq2Application · Apache

CVE-2022-22728

HIGH · 7.5 CVSS v3.1 Published 2022-08-25
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
84/100
Remediation priority · High
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
A flaw in Apache libapreq2 versions 2.16 and earlier could cause a buffer overflow while processing multipart form uploads. A remote attacker could send a request causing a process crash which could lead to a denial of service attack.

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

A buffer overflow vulnerability exists in Apache libapreq2 versions 2.16 and earlier when processing malicious multipart form upload requests. A remote attacker can exploit this by sending specially crafted multipart form data that overflows a buffer, causing the process to crash and resulting in denial of service.

MitigationUpgrade Apache libapreq2 to version 2.17 or later where the vulnerability is patched. If immediate upgrade is not feasible, implement input validation and size limits on multipart form uploads at the application or web server level to reduce attack surface.

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
Libapreq2Application
Affected:<= 2.16
FedoraOperating system
Affected:= 35= 36= 37
Debian LinuxOperating system
Affected:= 10.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check if libapreq2 is installed
    Run 'rpm -qa | grep libapreq' (RHEL/Fedora) or 'dpkg -l | grep libapreq' (Debian) to list installed libapreq packages
    Affected if No libapreq2 package is found, the system is not affected by this specific vulnerability
  2. Identify the installed libapreq2 version
    Run 'rpm -q libapreq2' (RHEL/Fedora) or 'dpkg -s libapreq2' (Debian) to display the installed version number
    Affected if The version number is 2.16 or earlier, indicating the vulnerable version is installed
  3. Verify if applications use libapreq2 for multipart processing
    Search application binaries and scripts for libapreq2 usage: 'ldd /path/to/application | grep apreq' or check application configuration for apreq modules
    Affected if Applications are linked against libapreq2 and process multipart form uploads, the vulnerability is potentially exploitable
  4. Check if multipart form uploads are accepted
    Review web server or application configuration for multipart/form-data handling settings and upload endpoints
    Affected if The application accepts multipart form uploads and uses libapreq2 to parse them, the attack vector is present

A system is affected if libapreq2 version 2.16 or earlier is installed and applications use it to process multipart form uploads.

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 2.16
Interim mitigation

Upgrade Apache libapreq2 to version 2.17 or later where the vulnerability is patched. If immediate upgrade is not feasible, implement input validation and size limits on multipart form uploads at the application or web server level to reduce attack surface.

Recommended fix Moderate confidence

libapreq2 version 2.17 or later

  1. 1. Identify all systems running libapreq2 version 2.16 or earlier
  2. 2. Upgrade libapreq2 to the latest stable version that includes the security fix (version 2.17 or later)
  3. 3. Rebuild and reinstall the library on affected systems
  4. 4. Restart any services or applications that depend on libapreq2 to load the fixed version
  5. 5. Verify the installed version is no longer vulnerable (should be > 2.16)

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

Fix this in Libapreq2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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