# CVE-2022-48468: Integer overflow in n/a > An attacker can cause a denial of service via an unsigned integer overflow in the protobuf-c library's parsing logic. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Apr 2023 - **Updated:** 13 Feb 2025 - **Also known as:** ALSA-2023:6621, ALSA-2023:6944, AZL-26159, CLSA-2025-1760548275, DEBIAN-CVE-2022-48468, GHSA-g29w-rp5q-p5vq, OESA-2023-1255, OESA-2023-1256, RHSA-2023:6621, RHSA-2023:6944, RHSA-2024:0406, RHSA-2024:3812, RLSA-2023:6621, SUSE-SU-2023:1979-1, SUSE-SU-2023:2143-1, UBUNTU-CVE-2022-48468, openSUSE-SU-2024:12885-1, openSUSE-SU-2026:10244-1 ## What is CVE-2022-48468? CVE-2022-48468 is a medium-severity vulnerability in n/a, published on 13 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description protobuf-c before 1.4.1 has an unsigned integer overflow in parse_required_member. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2022-48468? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `protobuf-c` | AlmaLinux:8 | All versions | 1.3.0-8.el8 | | `protobuf-c-compiler` | AlmaLinux:8 | All versions | 1.3.0-8.el8 | | `protobuf-c-devel` | AlmaLinux:8 | All versions | 1.3.0-8.el8 | | `protobuf-c` | AlmaLinux:9 | All versions | 1.3.3-13.el9 | | `protobuf-c-compiler` | AlmaLinux:9 | All versions | 1.3.3-13.el9 | | `protobuf-c-devel` | AlmaLinux:9 | All versions | 1.3.3-13.el9 | | `protobuf-c` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c-compiler` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c-compiler-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.3.0-8.el8 | | `protobuf-c` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.3.3-13.el9 | | `protobuf-c-compiler-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.3.3-13.el9 | | `protobuf-c-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.3.3-13.el9 | | `protobuf-c-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.3.3-13.el9 | | `protobuf-c-compiler` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.3.3-13.el9 | | `protobuf-c-compiler-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.3.3-13.el9 | | `protobuf-c-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.3.3-13.el9 | | `protobuf-c-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.3.3-13.el9 | | `protobuf-c-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.3.3-13.el9 | | `protobuf-c` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c-compiler` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c-compiler-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c-debuginfo` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c-debugsource` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c-devel` | Red Hat:rhel_eus:8.6::appstream | All versions | 0:1.3.0-8.el8_6 | | `protobuf-c` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c-compiler` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c-compiler-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c-debuginfo` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c-debugsource` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c-devel` | Red Hat:rhel_eus:8.8::appstream | All versions | 0:1.3.0-8.el8_8 | | `protobuf-c` | Rocky Linux:9 | All versions | 0:1.3.3-13.el9 | | `protobuf-c` | SUSE:Enterprise Storage 7 | All versions | 1.3.2-150200.3.3.1 | | `protobuf-c` | SUSE:Enterprise Storage 7.1 | All versions | 1.3.2-150200.3.3.1 | | `protobuf-c` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.3.0-150000.3.3.1 | | `protobuf-c` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 1.3.2-150200.3.3.1 | | `protobuf-c` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 1.3.2-150200.3.3.1 | | `protobuf-c` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.3.2-150200.3.3.1 | Products: Protobuf-C Project Protobuf-C. ## How do I fix CVE-2022-48468? Upgrade to a fixed version. ## Is CVE-2022-48468 being exploited? There is no known exploitation of CVE-2022-48468 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-48468 and fix it if it is affected. What it is: CVE-2022-48468 is a medium-severity vulnerability in n/a, published on 13 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-48468 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-48468/ (Markdown: https://insights.sbomify.com/CVE-2022-48468/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48468 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48468 - OSV: https://osv.dev/vulnerability/CVE-2022-48468 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-48468/ Summaries are generated and may contain mistakes; the official description above is the record.