# SUSE-SU-2020:3064-1: Security update for zeromq

> A malicious server can cause a memory leak or stack overflow in the ZeroMQ library, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2020

## What is SUSE-SU-2020:3064-1?

SUSE-SU-2020:3064-1 is a denial of service vulnerability in zeromq, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for zeromq fixes the following issues:

- Fixed a memory leak in client induced by malicious server(s) without CURVE/ZAP (bsc#1176257)
- Fixed a stack overflow in PUB/XPUB subscription store (bsc#1176258)

## Which versions are affected by SUSE-SU-2020:3064-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zeromq` | SUSE:Enterprise Storage 5 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Linux Enterprise Module for Advanced Systems Management 12 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Linux Enterprise Point of Sale 12 SP2 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Manager Client Tools 12 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Manager Proxy 3.2 | All versions | 4.0.4-15.6.1 |
| `zeromq` | SUSE:Manager Server 3.2 | All versions | 4.0.4-15.6.1 |

## How do I fix SUSE-SU-2020:3064-1?

Apply the vendor's patch.

## Is SUSE-SU-2020:3064-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2020:3064-1 is a denial of service vulnerability in zeromq, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2020:3064-1 in the wild and no public exploit code.

Affected product: zeromq. 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-2020-3064-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-3064-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2020:3064-1

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