# CVE-2022-41318: Information disclosure in n/a

> A buffer over-read in Squid's authentication helpers may leak cleartext credentials to clients in specific configurations.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** ALPINE-CVE-2022-41318, ALSA-2022:6775, ALSA-2022:6839, CLSA-2022-1665501369, CLSA-2022-1665501511, CLSA-2022-1665501668, CLSA-2022-1665501958, CLSA-2022-1665502073, CLSA-2022-1665680517, CLSA-2022-1665680640, DEBIAN-CVE-2022-41318, GHSA-394c-rr7q-6g78, RHSA-2022:6774, RHSA-2022:6775, RHSA-2022:6776, RHSA-2022:6777, RHSA-2022:6815, RHSA-2022:6839, RLSA-2022:6775, RLSA-2022:6839, UBUNTU-CVE-2022-41318

## What is CVE-2022-41318?

CVE-2022-41318 is a high-severity vulnerability in Squid-Cache Squid, published on 25 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer over-read was discovered in libntlmauth in Squid 2.5 through 5.6. Due to incorrect integer-overflow protection, the SSPI and SMB authentication helpers are vulnerable to reading unintended memory locations. In some configurations, cleartext credentials from these locations are sent to a client. This is fixed in 5.7.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2022-41318?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libecap` | AlmaLinux:8 | All versions | 1.0.1-2.module_el8.6.0+2741+01592ae8 |
| `libecap` | AlmaLinux:8 | All versions | 1.0.1-2.module_el8.6.0+3048+383bc947 |
| `libecap-devel` | AlmaLinux:8 | All versions | 1.0.1-2.module_el8.6.0+2741+01592ae8 |
| `libecap-devel` | AlmaLinux:8 | All versions | 1.0.1-2.module_el8.6.0+3048+383bc947 |
| `squid` | AlmaLinux:8 | All versions | 7:4.15-3.module_el8.6.0+3275+7a670b72.2 |
| `squid` | AlmaLinux:9 | All versions | 7:5.2-1.el9_0.2 |
| `squid` | Red Hat:enterprise_linux:7::server | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-migration-script` | Red Hat:enterprise_linux:7::server | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-sysvinit` | Red Hat:enterprise_linux:7::server | All versions | 7:3.5.20-17.el7_9.8 |
| `squid` | Red Hat:enterprise_linux:7::workstation | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-migration-script` | Red Hat:enterprise_linux:7::workstation | All versions | 7:3.5.20-17.el7_9.8 |
| `squid-sysvinit` | Red Hat:enterprise_linux:7::workstation | All versions | 7:3.5.20-17.el7_9.8 |
| `libecap` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:enterprise_linux:8::appstream | All versions | 7:4.15-3.module+el8.6.0+16749+7b6feaf0.2 |
| `squid-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 7:4.15-3.module+el8.6.0+16749+7b6feaf0.2 |
| `squid-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 7:4.15-3.module+el8.6.0+16749+7b6feaf0.2 |
| `squid` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.2-1.el9_0.2 |
| `squid-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.2-1.el9_0.2 |
| `squid-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 7:5.2-1.el9_0.2 |
| `libecap` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_e4s:8.1::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_e4s:8.1::appstream | All versions | 7:4.4-8.module+el8.1.0+16758+65e5269e.5 |
| `squid-debuginfo` | Red Hat:rhel_e4s:8.1::appstream | All versions | 7:4.4-8.module+el8.1.0+16758+65e5269e.5 |
| `squid-debugsource` | Red Hat:rhel_e4s:8.1::appstream | All versions | 7:4.4-8.module+el8.1.0+16758+65e5269e.5 |
| `libecap` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debugsource` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-devel` | Red Hat:rhel_eus:8.2::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `squid` | Red Hat:rhel_eus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+16757+26d6b59c.5 |
| `squid-debuginfo` | Red Hat:rhel_eus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+16757+26d6b59c.5 |
| `squid-debugsource` | Red Hat:rhel_eus:8.2::appstream | All versions | 7:4.4-8.module+el8.2.0+16757+26d6b59c.5 |
| `libecap` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |
| `libecap-debuginfo` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.1-2.module+el8.1.0+4044+36416a77 |

Products: Squid-Cache Squid.

## How do I fix CVE-2022-41318?

Upgrade to a fixed version.

## Is CVE-2022-41318 being exploited?

There is no known exploitation of CVE-2022-41318 in the wild and no public exploit code.

## Other vulnerabilities in Squid-Cache Squid

- [CVE-2025-62168](https://insights.sbomify.com/CVE-2025-62168/): Squid vulnerable to information disclosure via authentication credential leakage in error handling (critical 10.0)
- [CVE-2025-54574](https://insights.sbomify.com/CVE-2025-54574/): Squid's URN Handling can lead to Buffer Overflow (critical 9.3)
- [CVE-2026-33526](https://insights.sbomify.com/CVE-2026-33526/): Squid vulnerable to Denial of Service in ICP Request handling (critical 9.2)
- [CVE-2026-32748](https://insights.sbomify.com/CVE-2026-32748/): Squid has Denial of Service in ICP Response handling (high 8.7)
- [CVE-2023-50269](https://insights.sbomify.com/CVE-2023-50269/): SQUID-2023:10 Denial of Service in HTTP Request parsing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41318 and fix it if it is affected.

What it is: CVE-2022-41318 is a high-severity vulnerability in Squid-Cache Squid, published on 25 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41318 in the wild and no public exploit code.

Affected product: Squid-Cache Squid. 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-41318/ (Markdown: https://insights.sbomify.com/CVE-2022-41318/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41318
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41318
- OSV: https://osv.dev/vulnerability/CVE-2022-41318

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41318/
Summaries are generated and may contain mistakes; the official description above is the record.