You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
FastNetMon Community Edition through 1.2.9 has out-of-bounds memory access because it incorrectly parses BGP path attributes with the extended length flag set. In src/bgp_protocol.hpp, the parse_raw_bgp_attribute() function correctly identifies when extended_length_bit is set and sets length_of_length_field to 2, but then reads only a single byte for the attribute value length (attribute_value_length = value[2] at line 173). Per RFC 4271 Section 4.3, when the Extended Length bit is set, the Attribute Length field is two octets and the value should be read as a 16-bit big-endian integer from value[2] and value[3]. As a result, any attribute longer than 255 bytes has its length silently truncated to the low byte (e.g., 300 bytes = 0x012C is read as 0x2C = 44 bytes). The remaining 256 bytes are then misinterpreted as subsequent attributes, causing cascading parse failures and potential out-of-bounds memory access.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: FastNetMon Community Edition, Description: FastNetMon Community Edition hasta la versión 1.2.9 tiene acceso a memoria fuera de límites porque analiza incorrectamente los atributos de ruta BGP con el indicador de longitud extendida activado. En src/bgp_protocol.hpp, la función parse_raw_bgp_attribute() identifica correctamente cuando extended_length_bit está activado y establece length_of_length_field en 2, pero luego lee solo un byte para la longitud del valor del atributo (attribute_value_length = value[2] en la línea 173). Según la RFC 4271 Sección 4.3, cuando el bit de longitud extendida está activado, el campo de longitud del atributo es de dos octetos y el valor debe leerse como un entero big-endian de 16 bits de value[2] y value[3]. Como resultado, cualquier atributo de más de 255 bytes tiene su longitud truncada silenciosamente al byte bajo (por ejemplo, 300 bytes = 0x012C se lee como 0x2C = 44 bytes). Los 256 bytes restantes son luego malinterpretados como atributos subsiguientes, causando fallos de análisis en cascada y potencial acceso a memoria fuera de límites.
MITRE: https://lorikeetsecurity.com/blog/fastnetmon-cve-2026-48685-bgp-extended-length Types: Third Party Advisory
CVE Modified by CISA-ADP5/26/2026 5:16:42 PM
Action
Type
Old Value
New Value
Added
CVSS V3.1
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Added
CWE
CWE-130
New CVE Received from MITRE5/26/2026 12:16:26 PM
Action
Type
Old Value
New Value
Added
Description
FastNetMon Community Edition through 1.2.9 has out-of-bounds memory access because it incorrectly parses BGP path attributes with the extended length flag set. In src/bgp_protocol.hpp, the parse_raw_bgp_attribute() function correctly identifies when extended_length_bit is set and sets length_of_length_field to 2, but then reads only a single byte for the attribute value length (attribute_value_length = value[2] at line 173). Per RFC 4271 Section 4.3, when the Extended Length bit is set, the Attribute Length field is two octets and the value should be read as a 16-bit big-endian integer from value[2] and value[3]. As a result, any attribute longer than 255 bytes has its length silently truncated to the low byte (e.g., 300 bytes = 0x012C is read as 0x2C = 44 bytes). The remaining 256 bytes are then misinterpreted as subsequent attributes, causing cascading parse failures and potential out-of-bounds memory access.