dbcve.org
Portable RuntimeApplication · Apache

CVE-2023-49582

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-26
Fix available
A fix is available. Upgrade to 1.7.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Lax permissions set by the Apache Portable Runtime library on Unix platforms would allow local users read access to named shared memory segments, potentially revealing sensitive application data. This issue does not affect non-Unix platforms, or builds with APR_USE_SHMEM_SHMGET=1 (apr.h) Users are recommended to upgrade to APR version 1.7.5, which fixes this issue.

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

The Apache Portable Runtime (APR) library on Unix platforms sets overly permissive file permissions (typically 0666) on named shared memory segments, allowing any local unprivileged user to read potentially sensitive application data stored in these shared memory regions.

MitigationUpgrade to APR version 1.7.5 or later which fixes the default permissions. Alternatively, ensure builds use APR_USE_SHMEM_SHMGET=1 in apr.h to avoid this issue.

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:>= 0.9.0, < 1.7.5

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 inspect the version header file (apr_version.h) in your APR installation, typically found in /usr/include/apr-1/ or check the shared library version with `ldd --version` or `rpm -q apr`
    Affected if The installed version is lower than 1.7.5 and greater than or equal to 0.9.0
  2. Confirm APR shared memory is in use
    Identify processes that link against libapr (check via `ldd <executable>` or `nm <executable>`) and use APR's shared memory functions such as apr_shm_create, apr_shm_attach, or the underlying shmget calls. Review application documentation or source code for APR shared memory usage
    Affected if The application or service uses APR's shared memory functions and the system has unprivileged local users
  3. Inspect shared memory segment permissions
    Run `ipcs -m` to list all shared memory segments on the system. Check the `mode` column for the affected segments owned by the APR-linked application
    Affected if Any shared memory segment created by the application shows permissions of 0666 (world-readable/writable) rather than more restrictive permissions like 0600 or 0640

You are affected if your APR version is between 0.9.0 and 1.7.5 (exclusive) and your application uses APR shared memory functionality, allowing any local user to read the shared memory contents via ipcs inspection.

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 1.7.5 or later
Fixed in 1.7.5
Interim mitigation

Upgrade to APR version 1.7.5 or later which fixes the default permissions. Alternatively, ensure builds use APR_USE_SHMEM_SHMGET=1 in apr.h to avoid this issue.

Recommended fix High confidence

APR 1.7.5

  1. Identify all systems and applications that depend on the Apache Portable Runtime (APR) library
  2. Check the current APR version installed on affected systems using 'apr-config --version' or by inspecting the apr.h header file
  3. Download Apache Portable Runtime version 1.7.5 or later from the official Apache download mirrors (https://apr.apache.org/)
  4. Compile and install the updated APR library following the standard build process: ./configure, make, make install
  5. Update any applications that statically link to APR to rebuild against the new version
  6. Verify the fix by confirming the installed APR version is 1.7.5 or higher and that shared memory segments now have restricted permissions
  7. For systems using APR_USE_SHMEM_SHMGET=1 in apr.h, this vulnerability does not apply and no action is required

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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