Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 1.79% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2021
CVE-2021-22156High confidence
BlackBerry QNX Software Development Platform (SDP), QNX OS for Medical and QNX OS for Safety — Integer Overflow or Wraparound
BlackBerry · QNX Software Development Platform (SDP), QNX OS for Medical and QNX OS for Safety
9.0CriticalCVSS 3.1
Within 72 hours
Patch availableCritical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs BlackBerry QNX Software Development Platform (SDP), QNX OS for Medical and QNX OS for Safety and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
SEVD-2021-313-05 · CSAF 2.0 · revision 28.0.0 · finalSchneider Electric CPCERTBadAlloc Vulnerabilities
The vendor explicitly identifies these products as affected by this CVE.
- Niagara Framework Versions prior to v4.10u1 installed on JACE-8000 optional component of Schneider Electric TAC I/A Series
- Summary
- An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry® QNX Software Development Platform (SDP) version(s) 6.5.0SP1 and earlier, QNX OS for Medical 1.1 and earlier, and QNX OS for Safety 1.0.1 and earlier that could allow an attacker to potentially perform a denial of service or execute arbitrary code.
- Remediation
- Updates have been released to address the identified vulnerability Customers are urged to upgrade to Niagara 4.10u1. These updates are available on the Schneider Electric Exchange https://ecoxpert.se.com/ or by contacting your sales support channel or by contacting the Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com It is important that all TAC I/A Series Niagara customers for all supported platforms update their systems with these releases to mitigate risk. If you have any questions, please contact your Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com. As always, we highly recommend that TAC I/A Series Niagara customers running on an unsupported platform (such as Niagara G3/AX) take action to update their systems to a supported platform, ideally the 4.10u1 release of Niagara Framework. In addition to updating your system, Schneider Electric recommends that customers with affected products take the following steps to protect themselves: • Review and validate the list of users who are authorized and who can authenticate to Niagara. • Allow only trained and trusted persons to have physical access to the system, including devices that have connection to the system though the Ethernet port. • Consider using a VPN or other means to ensure secure remote connections into the network where the system is located, If remote connections are enabled. • Sign all modules and program objects provided by third-party teams. Review the Niagara Hardening Guide https://community.exchange.se.com/t5/Building-Automation-Knowledge/I-A-Series-Niagara-4-Hardening-Guide-Tips-to-Secure-an-I-A/ta-p/159287 for techniques on securing your installation.
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Patch available01
What, why and how
An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry® QNX Software Development Platform (SDP) version(s) 6.5.0SP1 and earlier, QNX OS for Medical 1.1 and earlier, and QNX OS for Safety 1.0.1 and earlier that could allow an attacker to potentially perform a denial of service or execute arbitrary code.
What
An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry® QNX Software Development Platform (SDP) version(s) 6.5.0SP1 and earlier, QNX OS for Medical 1.1 and earlier, and QNX OS for Safety 1.0.1 and earlier that could allow an attacker to potentially perform a denial of service or execute arbitrary code.
Why
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
An integer overflow vulnerability in the calloc() function of the C runtime library of affected versions of BlackBerry® QNX Software Development Platform (SDP) version(s) 6.5.0SP1 and earlier, QNX OS for Medical 1.1 and earlier, and QNX OS for Safety 1.0.1 and earlier that could allow an attacker to potentially perform a denial of service or execute arbitrary code.
Why
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Integer Overflow or Wraparound → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-190 ↗
CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Updates have been released to address the identified vulnerability Customers are urged to upgrade to Niagara 4.10u1. These updates are available on the Schneider Electric Exchange https://ecoxpert.se.com/ or by contacting your sales support channel or by contacting the Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com It is important that all TAC I/A Series Niagara customers for all supported platforms update their systems with these releases to mitigate risk. If you have any questions, please contact your Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com. As always, we highly recommend that TAC I/A Series Niagara customers running on an unsupported platform (such as Niagara G3/AX) take action to update their systems to a supported platform, ideally the 4.10u1 release of Niagara Framework. In addition to updating your system, Schneider Electric recommends that customers with affected products take the following steps to protect themselves: • Review and validate the list of users who are authorized and who can authenticate to Niagara. • Allow only trained and trusted persons to have physical access to the system, including devices that have connection to the system though the Ethernet port. • Consider using a VPN or other means to ensure secure remote connections into the network where the system is located, If remote connections are enabled. • Sign all modules and program objects provided by third-party teams. Review the Niagara Hardening Guide https://community.exchange.se.com/t5/Building-Automation-Knowledge/I-A-Series-Niagara-4-Hardening-Guide-Tips-to-Secure-an-I-A/ta-p/159287 for techniques on securing your installation.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 17 Aug 2021 · Last source change 22 Aug 2025, 15:20 UTC · CWE-190 · Integer Overflow or Wraparound
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2021-9303
Product sourceVendor CSAF · Schneider Electric CPCERT
Remediation sourceVendor CSAF · Schneider Electric CPCERT
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Schneider Electric CPCERT ↗
- Before
- QNX SDP 6.5.0 SP1 and earlier; QNX OS for Medical 1.1 and earlier; QNX OS for Safety 1.0.1 and earlier · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- QNX SDP 6.5.0 SP1 and earlier; QNX OS for Medical 1.1 and earlier; QNX OS for Safety 1.0.1 and earlier · Fixed: Updates have been released to address the identified vulnerability Customers are urged to upgrade to Niagara 4.10u1. These updates are available on the Schneider Electric Exchange https://ecoxpert.se.com/ or by contacting your sales support channel or by contacting the Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com It is important that all TAC I/A Series Niagara customers for all supported platforms update their systems with these releases to mitigate risk. If you have any questions, please contact your Schneider Electric support team at productsupport.NAM-BMS@schneider-electric.com. As always, we highly recommend that TAC I/A Series Niagara customers running on an unsupported platform (such as Niagara G3/AX) take action to update their systems to a supported platform, ideally the 4.10u1 release of Niagara Framework. In addition to updating your system, Schneider Electric recommends that customers with affected products take the following steps to protect themselves: • Review and validate the list of users who are authorized and who can authenticate to Niagara. • Allow only trained and trusted persons to have physical access to the system, including devices that have connection to the system though the Ethernet port. • Consider using a VPN or other means to ensure secure remote connections into the network where the system is located, If remote connections are enabled. • Sign all modules and program objects provided by third-party teams. Review the Niagara Hardening Guide https://community.exchange.se.com/t5/Building-Automation-Knowledge/I-A-Series-Niagara-4-Hardening-Guide-Tips-to-Secure-an-I-A/ta-p/159287 for techniques on securing your installation.
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.