# SUSE-SU-2018:3572-1: Security update for apache2-mod_nss

> Update required for Apache NSS module to support SQLite certificate database and TLS changes, tagged as security for distribution purposes.

- **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:** 30 Oct 2018

## What is SUSE-SU-2018:3572-1?

SUSE-SU-2018:3572-1 is a vulnerability in apache2-mod_nss, published on 30 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for apache2-mod_nss fixes the following issues:

Due to the update of mozilla-nss apache2-mod_nss needs to be updated to change
to the SQLite certificate database, which is now the default (bsc#1108771).
Because of that this update is tagged as security, to reach customers that only
install secuirty updates.

Other changes contained:

- Require minimal NSS version of 3.25 because of SSLv2 changes (bsc#993642)
- Add support for SHA384 TLS ciphers (bsc#863035)
- Remove deprecated NSSSessionCacheTimeout option from mod_nss.conf.in (bsc#998176)
- Change ownership of the gencert generated NSS database so apache can read it (bsc#998180)
- Use correct configuration path in mod_nss.conf.in (bsc#996282)
- Generate dummy certificates if there aren't any in mod_nss.d (bsc#998183)

## Which versions are affected by SUSE-SU-2018:3572-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache2-mod_nss` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 1.0.14-10.17.2 |

## How do I fix SUSE-SU-2018:3572-1?

Apply the vendor's patch.

## Is SUSE-SU-2018:3572-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2018:3572-1 is a vulnerability in apache2-mod_nss, published on 30 Oct 2018. 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-2018:3572-1 in the wild and no public exploit code.

Affected product: apache2-mod_nss. 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-2018-3572-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-3572-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2018:3572-1

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