Bug ID 669974: Encoding binary data using ASN1::encode may truncate result

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3.2

Opened: Jun 19, 2017
Severity: 3-Major
Related AskF5 Article:
K90395411

Symptoms

When using ASN1::encode to encode one or more values, and where the encoding of any of these values results in a representation containing a NUL ('\x0') byte, the overall result that is presented to the iRule does not include the entire set of encoded values and is truncated at the first NUL byte.

Impact

Encoding results in the wrong/truncated value.

Conditions

-- Using ASN1::encode with binary values (e.g., INTEGER). -- Encoded results contain a NUL ('\x0') byte.

Workaround

It is possible to encode the problematic values using an alternative method.

Fix Information

ASN1::encode now correctly encodes binary values.

Behavior Change