Illegal Meta Character in Value

Greg,

 

What is the violation you are receiving from ASM on this. The Meta-Character 0xd is actually CR (carriage return) in actual character.

 

 

Mike

Hello Mike,

 

 

Thank you for replying so fast. I will claim ignorance on this, I am not receiving a violation. Currently the ASM is in tightening and I am manually building the policy. When I went in this morning I had 8 Illegal Meta Character's that I had to learn, which normally I copy the Parameter name and meta character then create it under the parameter list. I have seen parameter's with 0x20 and have been able to add them fine. I have never seen one with 0xd in the name. I did research and see that it was a carriage return but was unsure how to type that into the name of the parameter. Sorry my question was unclear. Please let me know if I can provide anything to make this easier.

 

 

Thank you,

 

Greg

No problem, is the request above the actual request that contains the meta-character? Do you mind telling me what type of application request this is?

That is correct, the request above contains the meta-characters. The application is Peoplesoft 9.1.

Have you tried allowing the character as a part of the header, I am not very familiar with Peoplesoft but that does not look like it is a parameter name or value.

That's a multipart POST request. ASM should parse the parameter names and values correctly. Generally, the carriage return and/or line feed characters would be in the parameter value.

 

 

Greg, can you post an anonymized copy of the full request headers and payload?

 

 

Thanks, Aaron

Hello guys,

 

 

Thank you for responding to my issue but I was able to solve my issue by creating my own wildcard for Message ID's.

 

 

-Greg