CVE-2021-44522
No exploitation reported by the sources we read.
- Published2021-12-14
- WeaknessCWE-668
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability has been identified in SiPass integrated V2.76 (All versions), SiPass integrated V2.80 (All versions), SiPass integrated V2.85 (All versions), Siveillance Identity V1.5 (All versions), Siveillance Identity V1.6 (All versions < V1.6.284.0). Affected applications insufficiently limit the access to the internal message broker system. This could allow an unauthenticated remote attacker to subscribe to arbitrary message queues.
Timeline
dates in UTC- 2021-12-1412:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-44522?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-44522?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.76 | = 2.76 | no fix published | NVD |
| 2.80 | = 2.80 | no fix published | NVD |
| 2.85 | = 2.85 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.6 | ≥ 1.6, ≤ 1.6.280.0 | no fix published | NVD |
| 1.5 | = 1.5 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Siemens Siveillance Identity
Siveillance Identity V1.5 · Siveillance Identity V1.6
Siemens SiPass Integrated
SiPass integrated V2.76 · SiPass integrated V2.80 · SiPass integrated V2.85
Fix
- Vendor fix CISA ICSA-21-350-14 · 1 productUpdate to V1.6.284.0 or later version
- Vendor fix CISA ICSA-21-350-14 · 1 productUpdate to V1.5 SP4 and apply the Credential Patch Tool: https://support.industry.siemens.com/cs/ww/en/view/109801824/
- Vendor fix CISA ICSA-21-350-19 · 1 productUpdate to V2.76 SP2 and then download and execute the SiPass integrated Component Manager: https://support.industry.siemens.com/cs/ww/en/view/109802587/
- Vendor fix CISA ICSA-21-350-19 · 2 productsDownload and execute the SiPass integrated Component Manager: https://support.industry.siemens.com/cs/ww/en/view/109802587/
Advisories and patches
- cert-portal.siemens.comVendor Advisory
- cert-portal.siemens.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.17.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- CNAweakness (CWE)CWE-668read 2026-10-23
- FIRST EPSSEPSS score1.4 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2021-12-14
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2021-44522?
Is CVE-2021-44522 actively exploited?
What is the CVSS score for CVE-2021-44522?
Running Siemens SiPass Integrated? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.