dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-2961

HIGH · 7.3 CVSS v3.1 Published 2024-04-17
Fix available
A fix is available. Upgrade to 2.40 or later.
See remediation →
78/100
Remediation priority · High
High EPSS 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
The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.

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

Buffer overflow vulnerability in GNU C Library's iconv() function allows up to 4-byte overflow when converting to ISO-2022-CN-EXT character set, potentially enabling application crash or adjacent memory corruption.

MitigationUpdate glibc to version 2.40 or later; identify and test applications using ISO-2022-CN-EXT charset conversion to verify fix effectiveness.

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
Debian LinuxOperating system
Affected:= 10.0
GlibcFramework / library
Affected:>= 2.1.93, < 2.40
Active Iq Unified ManagerApplication
Affected:all versions
Hci H300s FirmwareOperating system
Affected:all versions
Hci H500s FirmwareOperating system
Affected:all versions
Hci H700s FirmwareOperating system
Affected:all versions
Hci H410s FirmwareOperating system
Affected:all versions
Hci H410c FirmwareOperating system
Affected:all versions

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Identify the installed glibc version
    Run `ldd --version` or examine the libc shared library with `ls -la /lib/x86_64-linux-gnu/libc.so.*` or check `/usr/lib/libc.so.6`
    Affected if The reported version is lower than 2.40 and greater than or equal to 2.1.93 (for Linux systems) or the product is Debian 10.0 (which ships with a vulnerable glibc)
  2. Locate all glibc library files on the system
    Use `find / -name 'libc-*' -o -name 'libc.so*' 2>/dev/null` to find all glibc copies, especially in non-standard paths
    Affected if Any glibc library found is version 2.1.93 through 2.39 (exclusive of 2.40)
  3. Determine if any applications use the iconv() function
    Search application code or binaries for iconv calls: `grep -r 'iconv' /path/to/applications/` or use `ldd /path/to/binary` to list shared library dependencies
    Affected if Applications link against glibc and call iconv() functions
  4. Identify if ISO-2022-CN-EXT charset conversion is in use
    Review application logs, configuration, or source code for usage of 'ISO-2022-CN-EXT' or 'ISO2022CNEXT' as a target charset in iconv_open() calls
    Affected if Any application performs character set conversion to ISO-2022-CN-EXT using glibc's iconv()
  5. Check NetApp product firmware versions (if applicable)
    For affected NetApp products (H300s, H500s, H700s, H410s, H410c, Active IQ Unified Manager), consult the product's version or firmware information page
    Affected if The product is any version of the listed NetApp firmware or software (all versions are affected per the advisory)

The environment is affected if glibc version 2.1.93 through 2.39 is installed AND any application uses the iconv() function to convert to the ISO-2022-CN-EXT character set, or if the system runs a listed NetApp product at any version.

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

Update glibc to version 2.40 or later; identify and test applications using ISO-2022-CN-EXT charset conversion to verify fix effectiveness.

Recommended fix High confidence

Glibc 2.40 or later

  1. Check the current glibc version installed (ldd --version or /lib/x86_64-linux-gnu/libc.so.6)
  2. Update the package repository indexes (apt-get update on Debian-based systems)
  3. Upgrade the glibc package to version 2.40 or later using the appropriate package manager (e.g., apt-get upgrade, yum update, or dnf update)
  4. Reboot the system to ensure the new glibc library is loaded
  5. Verify the installed glibc version is 2.40 or later
Caveat Major glibc upgrades can cause compatibility issues with older binaries or applications linked against the previous glibc version; test critical applications after upgrade

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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