dbcve.org
LibpeconvApplication · Libpeconv Project

CVE-2023-23462

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-15
Fix available
A fix is available. Upgrade to 2022-11-30 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Libpeconv – integer overflow, before commit 75b1565 (30/11/2022).

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 confidence

Integer overflow vulnerability in libpeconv library used for parsing PE (Portable Executable) files on Windows. The overflow occurs during size calculations when processing PE headers, potentially allowing heap buffer overflows and memory corruption that could lead to arbitrary code execution.

MitigationUpgrade libpeconv to a version after commit 75b1565 (November 30, 2022) or apply the specific fix from that commit which adds proper integer overflow checks before memory allocation operations.

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
LibpeconvApplication
Affected:< 2022-11-30

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate libpeconv library files
    Search for libpeconv.dll (Windows) or libpeconv.so (Linux) in application directories, system paths, and common library locations. Use commands like 'dir /s /b libpeconv*' on Windows or 'find / -name "libpeconv*" 2>/dev/null' on Linux.
    Affected if The library file exists on the system and the version is earlier than the November 30, 2022 fix commit.
  2. Determine libpeconv version or build date
    If the library file is found, right-click to view Properties > Details tab (Windows) or use 'file' and 'strings' commands to extract version info. Look for version strings, timestamps, or build dates embedded in the binary.
    Affected if The version string or binary timestamp predates November 2022, indicating an unpatched build.
  3. Identify applications using libpeconv
    Search for executables or DLLs that dynamically link to libpeconv. On Windows, use tools like 'dumpbin /dependents' or 'Dependencies.exe' to list dependencies. On Linux, use 'ldd' or 'readelf -d' on suspected binaries.
    Affected if An application loads libpeconv.dll/so and the library version is before the fix date.
  4. Check source code version if available
    If you have access to the libpeconv source code used in your build, check the commit history or version file. Look for commit 75b1565 or later, or check the date in version metadata files.
    Affected if The source code corresponds to a version earlier than the November 30, 2022 commit containing the overflow check fix.
  5. Verify PE parsing code paths
    Audit any custom code that calls libpeconv functions related to header parsing (such as peconv::parse_pe_headers, peconv::load_pe, or similar functions that perform size calculations on PE structures).
    Affected if The application performs PE parsing operations using libpeconv and the library version is unpatched.

The environment is affected if libpeconv (any version of the library that parses PE files) is installed and its build date or version is earlier than November 30, 2022.

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 2022-11-30 or later
Fixed in 2022-11-30
Interim mitigation

Upgrade libpeconv to a version after commit 75b1565 (November 30, 2022) or apply the specific fix from that commit which adds proper integer overflow checks before memory allocation operations.

Recommended fix High confidence

Libpeconv version including commit 75b1565 (2022-11-30) or later

  1. Identify all projects or applications that depend on Libpeconv
  2. Check current Libpeconv version in use (library file date or version metadata)
  3. Locate the Libpeconv repository or package manager distribution
  4. Upgrade Libpeconv to a version released on or after November 30, 2022 (commit 75b1565)
  5. Rebuild or recompile any projects that link against Libpeconv
  6. Verify the upgrade was successful by checking the library version or reviewing the source code at commit 75b1565

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

Fix this in Libpeconv Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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