← Back
CWE-167

5 CVEs • Abstraction: Base

Improper Handling of Additional Special Element

The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.

JSON object

Loading...

CVEs (5)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Microsoft
2Exchange Server
Exchange Server Subscription Edition
Jun 17, 2026
Aug 12, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
Improper handling of additional special element in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.
1Juniper
1Junos
Jun 17, 2026
Apr 9, 2025
8.7 HIGH· v4
7.5 HIGH· v3
N/A· v2
An Improper Handling of Additional Special Element vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series with MS-MPC, MS-MIC and SPC3, and SRX Series, allows an unauthenticated, ne...Show more
An Improper Handling of Additional Special Element vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series with MS-MPC, MS-MIC and SPC3, and SRX Series, allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). If the SIP ALG processes specifically formatted SIP invites, a memory corruption will occur which will lead to a crash of the FPC processing these packets. Although the system will automatically recover with the restart of the FPC, subsequent SIP invites will cause the crash again and lead to a sustained DoS. This issue affects Junos OS on MX Series and SRX Series:  * all versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10, * 22.2 versions before 22.2R3-S6, * 22.4 versions before 22.4R3-S5, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S3, * 24.2 versions before 24.2R1-S2, 24.2R2.Show less
1Freebsd
1Freebsd
Jun 17, 2026
Sep 6, 2023
N/A· v4
7.5 HIGH· v3
N/A· v2
In pf packet processing with a 'scrub fragment reassemble' rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed. That is, a packet with multiple fragment extensio...Show more
In pf packet processing with a 'scrub fragment reassemble' rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed. That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is. As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.Show less
1Squidex.io
1Squidex
Jun 17, 2026
Jul 10, 2023
N/A· v4
4.3 MEDIUM· v3
N/A· v2
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.
1Squidex.io
1Squidex
Jun 17, 2026
Feb 2, 2023
N/A· v4
6.1 MEDIUM· v3
N/A· v2
Improper Handling of Additional Special Element in GitHub repository squidex/squidex prior to 7.4.0.