evidence stringclasses 3
values | test_case dict | source_code stringclasses 3
values | bug_root_cause stringclasses 3
values | defect_category stringclasses 3
values | validation_result stringclasses 1
value | affected_information_element stringclasses 3
values |
|---|---|---|---|---|---|---|
For this input, the buffer has 7 octets and the declared payload length is 4, so len(data) < length is false. The subsequent slice returns only three payload octets instead of rejecting the IE. | {
"protocol_name": "PFCP (N4)",
"message_type": "Recovery Time Stamp IE",
"encoded_message_hex": "00600004010203",
"test_condition": "The IE header declares a four-octet value, but only three value octets follow the header.",
"expected_behavior": "Reject the IE because the available value is shorter than the ... | def parse_ie(data):
ie_type = int.from_bytes(data[0:2], 'big')
length = int.from_bytes(data[2:4], 'big')
if len(data) < length:
raise ValueError('truncated IE')
return ie_type, data[4:4 + length]
| The truncation check compares the total buffer length with the payload length, without accounting for the four-octet IE header. As a result, a short payload can pass the check. | 长度处理错误 | 失败 | Recovery Time Stamp IE value |
The input flags octet is 0x02. The condition flags & 0x03 therefore reads the first four IPv6 octets as IPv4, leaving only twelve octets for the subsequent IPv6 conversion, which requires sixteen. | {
"protocol_name": "PFCP (N4)",
"message_type": "F-SEID IE",
"encoded_message_hex": "0039001902010203040506070820010db8000000000000000000000001",
"test_condition": "The F-SEID flags indicate IPv6 is present and IPv4 is absent; the value contains a SEID followed by a 16-octet IPv6 address.",
"expected_behavior... | import ipaddress
def parse_fseid(data):
if len(data) < 4:
raise ValueError('truncated IE header')
ie_type = int.from_bytes(data[0:2], 'big')
if ie_type != 57:
raise ValueError('unexpected IE type')
length = int.from_bytes(data[2:4], 'big')
value = data[4:4 + length]
if len(value... | The IPv4 presence check uses mask 0x03, which is set when either the IPv4 or IPv6 flag is present. It should test only the IPv4 flag, so an IPv6-only value is incorrectly consumed as if it included IPv4. | 可选字段处理错误 | 失败 | F-SEID IPv4 and IPv6 address fields |
With input 0060, the length slice data[2:4] is empty and int.from_bytes returns zero. The code then returns an IE with an empty value instead of rejecting the incomplete header. | {
"protocol_name": "PFCP (N4)",
"message_type": "Generic PFCP IE header",
"encoded_message_hex": "0060",
"test_condition": "The input ends after the two-octet IE type and contains neither octet of the required length field.",
"expected_behavior": "Reject the input as a truncated IE header before interpreting ... | def parse_ie(data):
if len(data) < 2:
raise ValueError('missing IE type')
ie_type = int.from_bytes(data[0:2], 'big')
length = int.from_bytes(data[2:4], 'big')
value = data[4:4 + length]
if len(value) != length:
raise ValueError('truncated IE value')
return ie_type, value
| The initial boundary check verifies only that the two-octet IE type is present. It does not require the complete four-octet IE header before reading the length field. | 边界条件处理错误 | 失败 | PFCP IE length field |
5G Core Network Protocol Encoding and Decoding and Information Element Code Verification Benchmark
This benchmark contains source code examples related to 5G core network protocol message encoding and decoding, as well as information element parsing and validation. It focuses on defect-prone cases involving length handling, optional fields, and boundary conditions. Each case pairs test inputs with expected constraints and records validation results, defect categories, affected information elements, root causes, and code evidence, supporting evaluation of models' protocol verification and root-cause analysis capabilities.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| evidence | string | Code location, key logic, or validation observation supporting the defect finding. |
| test_case | object | Original test input and expected constraints used to verify protocol handling behavior. |
| source_code | string | Source code to verify for protocol encoding and decoding or information element parsing and validation. |
| bug_root_cause | string | Code logic or constraint handling that causes protocol behavior to deviate from expectations. |
| defect_category | string | Category of the identified protocol handling defect. |
| validation_result | string | Whether code execution or rule checking conforms to the expected constraints. |
| affected_information_element | string | Name of the information element with a parsing, encoding, or validation issue; use unknown when it cannot be determined. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- 33