# CVE-2022-38658: HCL BigFix Server Automation (SA) is affected by a security vulnerability around Notification Service

> Attackers can read SMTP credentials in clear text if the Notification Service is installed on Windows, exposing operator sensitive data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-4vwj-7pm2-257c

## What is CVE-2022-38658?

CVE-2022-38658 is a high-severity vulnerability in HCL Software BigFix Server Automation, published on 22 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BigFix deployments that have installed the Notification Service on Windows are susceptible to disclosing SMTP BigFix operator's sensitive data in clear text. Operators who use Notification Service related content from BES Support are at risk of leaving their SMTP sensitive data exposed.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2022-38658?

It affects 1 product.


Products: Hcltech Bigfix Server Automation.

## How do I fix CVE-2022-38658?

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

## Is CVE-2022-38658 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38658 and fix it if it is affected.

What it is: CVE-2022-38658 is a high-severity vulnerability in HCL Software BigFix Server Automation, published on 22 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38658 in the wild and no public exploit code.

Affected product: HCL Software BigFix Server Automation. 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-2022-38658/ (Markdown: https://insights.sbomify.com/CVE-2022-38658/index.md)
```

## Sources

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

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