# SUSE-SU-2016:0267-1: Security update for rubygem-mail-2_4

> An attacker can inject SMTP commands via recipient email addresses in the Ruby mail library, potentially altering email delivery.

- **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:** 27 Jan 2016

## What is SUSE-SU-2016:0267-1?

SUSE-SU-2016:0267-1 is a vulnerability in rubygem-mail-2_4, published on 27 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for rubygem-mail-2_4 fixes the following issues:

* bsc#959129: SMTP Injection via recipient email addresses

## Which versions are affected by SUSE-SU-2016:0267-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rubygem-mail-2_4` | SUSE:Lifecycle Management Server 1.3 | All versions | 2.4.4-0.10.2 |
| `rubygem-mail-2_4` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.4.4-0.10.2 |
| `rubygem-mail-2_4` | SUSE:Studio Onsite 1.3 | All versions | 2.4.4-0.10.2 |
| `rubygem-mail-2_4` | SUSE:WebYast 1.3 | All versions | 2.4.4-0.10.2 |

## How do I fix SUSE-SU-2016:0267-1?

Apply the vendor's patch.

## Is SUSE-SU-2016:0267-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2016:0267-1 is a vulnerability in rubygem-mail-2_4, published on 27 Jan 2016. 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-2016:0267-1 in the wild and no public exploit code.

Affected product: rubygem-mail-2_4. 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-2016-0267-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2016-0267-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2016:0267-1

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