# CVE-2024-12174: Other in Security Center

> An authenticated privileged attacker can intercept Security Center emails via a rogue SMTP server due to improper certificate validation.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2024
- **Updated:** 10 Dec 2024
- **Also known as:** GHSA-hj9q-mj9c-fcp4

## What is CVE-2024-12174?

CVE-2024-12174 is a low-severity vulnerability in Tenable Security Center, published on 9 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Improper Certificate Validation vulnerability exists in Tenable Security Center where an authenticated, privileged attacker could intercept email messages sent from Security Center via a rogue SMTP server.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-12174?


## How do I fix CVE-2024-12174?

No fix has been published for CVE-2024-12174 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-12174 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12174 and fix it if it is affected.

What it is: CVE-2024-12174 is a low-severity vulnerability in Tenable Security Center, published on 9 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12174 in the wild and no public exploit code.

Affected product: Tenable Security Center. 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-2024-12174/ (Markdown: https://insights.sbomify.com/CVE-2024-12174/index.md)
```

## Sources

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

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