# SUSE-SU-2023:3183-1: Security update for python-pip

> Removal of .exe files from the python-pip RPM package to prevent false positives in security scanners.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2023

## What is SUSE-SU-2023:3183-1?

SUSE-SU-2023:3183-1 is a vulnerability in python-pip, published on 3 Aug 2023. 

### Official description

This update for python-pip fixes the following issues:

- Removed .exe files from the RPM package, to prevent issues with security scanners (bsc#1212015).

## Which versions are affected by SUSE-SU-2023:3183-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-pip` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 20.0.2-150100.6.21.1 |
| `python-pip` | SUSE:Manager Proxy 4.2 | All versions | 20.0.2-150100.6.21.1 |
| `python-pip` | SUSE:Manager Server 4.2 | All versions | 20.0.2-150100.6.21.1 |

## How do I fix SUSE-SU-2023:3183-1?

Apply the vendor's patch.

## Is SUSE-SU-2023:3183-1 being exploited?

There is no known exploitation of SUSE-SU-2023:3183-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2023:3183-1 and fix it if it is affected.

What it is: SUSE-SU-2023:3183-1 is a vulnerability in python-pip, published on 3 Aug 2023. 
Exploitation: There is no known exploitation of SUSE-SU-2023:3183-1 in the wild and no public exploit code.

Affected product: python-pip. 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/SUSE-SU-2023-3183-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-3183-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2023:3183-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2023-3183-1/
Summaries are generated and may contain mistakes; the official description above is the record.