CVE-2022-29550 json
An issue was discovered in Qualys Cloud Agent 4.8.0-49.
published 4y ago modified 4mo ago also EUVD-2022-33885
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
An issue was discovered in Qualys Cloud Agent 4.8.0-49. It writes "ps auxwwe" output to the /var/log/qualys/qualys-cloud-agent-scan.log file. This may, for example, unexpectedly write credentials (from environment variables) to disk in cleartext. NOTE: there are no common circumstances in which qualys-cloud-agent-scan.log can be read by a user other than root; however, the file contents could be exposed through site-specific operational practices. The vendor does NOT characterize this as a vulnerability because the ps data collection is intentional, and would only capture credentials on a machine that was already affected by the CWE-214 weakness
Is CVE-2022-29550 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
blog.qualys.com
/vulnerabilities-threat-research
vendor-advisory
-
blog.qualys.com
/product-tech/2022/08/15/qualys-security-updates-cloud-agent-for-linux
vendor-advisory
-
seclists.org
/fulldisclosure/2022/Sep/10
mailing-list, third-party-advisory
-
packetstormsecurity.com
/files/168367/Qualys-Cloud-Agent-Arbitrary-Code-Execution.html
third-party-advisory
Sources
- CVE List CVE-2022-29550
- NVD CVE-2022-29550
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.