CVE-2023-31122
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 · uneditedOut-of-bounds Read vulnerability in mod_macro of Apache HTTP Server.This issue affects Apache HTTP Server: through 2.4.57.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in mod_macro, an optional module for Apache HTTP Server. This vulnerability could allow an attacker to read sensitive memory contents beyond buffer boundaries, potentially exposing configuration details, session tokens, or other in-memory data. The issue affects all Apache HTTP Server versions through 2.4.57.
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= 10.0< 2.4.58= 38CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if mod_macro is loaded in ApacheRun 'apache2ctl -M' (Debian/Ubuntu) or 'httpd -M' (RHEL/CentOS/Fedora) and look for 'macro_module' in the list of loaded modules.Affected if mod_macro (macro_module) appears in the loaded modules list
-
Check Apache HTTP Server versionRun 'apache2 -v' (Debian/Ubuntu) or 'httpd -v' (RHEL/CentOS/Fedora) to retrieve the installed version number.Affected if The version shown is lower than 2.4.58 (for example, 2.4.57 or earlier)
-
Verify mod_macro configuration filesSearch for 'mod_macro' or 'macro' references in Apache configuration files under /etc/apache2/mods-enabled/ (Debian) or /etc/httpd/conf.modules.d/ (RHEL). Alternatively, inspect the main httpd.conf for 'LoadModule macro_module' statements.Affected if mod_macro is explicitly loaded via LoadModule directive or enabled in the configuration
-
Check for macro definitions in useSearch configuration directories (/etc/apache2, /etc/httpd) for .macro files or 'Macro' directives in config files using 'grep -r "Macro" /etc/apache2/' or similar.Affected if Macro definitions are present in any Apache configuration files
-
Check system package version on affected distributionsOn Debian 10, run 'dpkg -l | grep apache2'. On Fedora 38, run 'rpm -qa | grep httpd' to inspect the installed package version.Affected if The installed package version corresponds to an Apache version below 2.4.58
You are affected if mod_macro is loaded/enabled AND your Apache version is below 2.4.58, or if you are running Debian 10.0 or Fedora 38 with Apache and mod_macro is present.
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 · scoped2.4.58
Upgrade Apache HTTP Server to version 2.4.58 or later. If immediate patching is not feasible, disable the mod_macro module if not required in the server configuration.
Apache HTTP Server 2.4.58 or later
- 1. Identify current Apache HTTP Server version using: httpd -v or apache2 -v
- 2. For Debian 10.0: Run apt update && apt install apache2 to upgrade to the latest available version (2.4.58 or later)
- 3. For Fedora 38: Run dnf update httpd to upgrade to the latest available version (2.4.58 or later)
- 4. After upgrade, restart Apache service: systemctl restart httpd (or systemctl restart apache2 on Debian)
- 5. Verify the new version is 2.4.58 or later using: httpd -v
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31122 — 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-2023-31122 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