dbcve.org
LibpeconvApplication · Libpeconv Project

CVE-2023-23461

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 – access violation, before commit b076013 (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

Libpeconv, a library for processing Windows PE (Portable Executable) files, contains an access violation vulnerability. The issue was addressed in commit b076013 (30/11/2022). Access violations in PE parsing libraries can potentially allow attackers to read or write to arbitrary memory locations, possibly leading to code execution.

MitigationUpdate libpeconv to a version after commit b076013 (November 30, 2022). Review all code paths using libpeconv to ensure the updated library is properly integrated and does not introduce regressions.

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 binaries or libraries in your environment
    Search for files named libpeconv.dll, libpeconv.lib, or similar PE processing libraries. Check application directories, system folders, and dependencies. Use 'dir /s /b libpeconv*' or file system search tools.
    Affected if libpeconv DLL or library file exists and its version/build date predates November 30, 2022
  2. Check libpeconv version or file timestamp
    Right-click the libpeconv DLL and select Properties > Details. Note the 'Product version', 'File version', or 'Date created/modified' fields. Alternatively, use a PE viewer tool to examine the build timestamp in the PE header.
    Affected if The version field shows a date before 2022-11-30, or the PE header timestamp is earlier than the fix commit date
  3. Identify applications using libpeconv
    Review application dependency lists, manifest files, or installer records to identify software that links against libpeconv. Check the application's third-party license or components list.
    Affected if An application depends on libpeconv and the library version cannot be confirmed as post-fix
  4. Verify build system integration if compiling from source
    If your project compiles libpeconv from source, check the git commit history or source file dates. Look for the presence of commit b076013 or files modified after November 30, 2022.
    Affected if The libpeconv source code in use predates the November 30, 2022 commit

Your environment is affected if any libpeconv binary or library in use has a version or build date 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

Update libpeconv to a version after commit b076013 (November 30, 2022). Review all code paths using libpeconv to ensure the updated library is properly integrated and does not introduce regressions.

Recommended fix Moderate confidence

Libpeconv commit b076013 (2022-11-30) or any subsequent release

  1. Identify all locations where Libpeconv is used in your project or dependencies
  2. Check the current version or commit hash of Libpeconv in use
  3. If using a package manager or dependency management system, update to a version of Libpeconv released after November 30, 2022
  4. If using git submodule or direct inclusion, verify the commit is b076013 or later
  5. Rebuild and test the application to ensure the update resolves the access violation issue

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

Fix this in Libpeconv Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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