Disable buffer overflow in json parameters

Question

Hi 
In a file upload using api we allow the file name in base64 encoding. 
However this triggers the Generic buffer overflow attempt 1. 
As of this post it seems signature at json parameter level cannot be disabled. 
https://devcentral.f5.com/questions/disable-attack-signature-on-particular-json-parametercomment77010
Has there been any change in this? I am using v12? 
In my json content profile I do not see the buffer overflow sig at all on filtering with the name.

lior_rotkovtic1 · Answer

try serach sig ID 200011000  in the "filter signatues by name or ID"&nbsp;

lior_rotkovitch · Answer

try serach sig ID 200011000  in the "filter signatues by name or ID"&nbsp;

allwyn_mascaren · Answer

I tried, the thing is this box with the problem has not updated the ASM signatures. 
My lab device with v12 and updated ASM sig does not even have that attempt 1 buffer overflow sig anymore, but only attempt 27 28 and so on.

allwyn_mascaren · Answer

I tried, the thing is this box with the problem has not updated the ASM signatures. 
My lab device with v12 and updated ASM sig does not even have that attempt 1 buffer overflow sig anymore, but only attempt 27 28 and so on.

lior_rotkovitch · Answer

not even here ? : Security  ››  Options : Application Security : Attack Signatures : Attack Signature List &nbsp;
also, try accepitng the request from the request log - where it got block. this should disable the signautre so that it will not block&nbsp;

Forum Discussion

Disable buffer overflow in json parameters

Recent Discussions

About ePVA question ?

How does the BIG-IP process multiple LTM policies on a virtual server?

WAF for APM Oauth Authorization VS

F5 on AWS Cloud

SSH/SFTP VIP on LTM

Related Content

IIS 6.0 WebDAV Buffer Overflow

Brute Force protection for single parameter like OTP

Disabling Weak Ciphers

Disable below cipher

Disabling Specific Weak Cipher Suites