Last Modified: Oct 04, 2024
Affected Product(s):
BIG-IP APM
Known Affected Versions:
15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1
Opened: Mar 23, 2021 Severity: 4-Minor
URI normalization issue when using attributeNode to access attribute values.
Web application does not work as expected.
Using attributeNode to access attribute value in web applications
Use custom iRule to fix this issue. There is no generic iRule for this issue, but here is a sample iRule: XXXX is the file which usage attributeNode. when REWRITE_REQUEST_DONE { if { [HTTP::path] ends_with "XXXX" } { # log "URI=([HTTP::path])" # Found the file to modify REWRITE::post_process 1 } } when REWRITE_RESPONSE_DONE { set strt [string first {<script>try} [REWRITE::payload]] if {$strt > 0} { REWRITE::payload replace $strt 0 { <script> (function (){ var old_F5_Inflate_value = F5_Inflate_value; F5_Inflate_value = function (o,sw,incr,v) { if (o && o.ownerDocument) { if (o.name == 'action') { if (o.ownerElement) { F5_Inflate_action(o.ownerElement,incr,v); } } } return old_F5_Inflate_value.apply(this,arguments) } })(); </script> } } }
None