Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CEF escaping is not consistent or implemented on extension fields #9

Open
hanvyj opened this issue Sep 25, 2020 · 1 comment
Open

Comments

@hanvyj
Copy link
Contributor

hanvyj commented Sep 25, 2020

There escaping doesn't seem consistent with [the CEF standard].(https://kc.mcafee.com/resources/sites/MCAFEE/content/live/CORP_KNOWLEDGEBASE/78000/KB78712/en_US/CEF_White_Paper_20100722.pdf)

For example, there's no | character escaping in the prefix fields. There's also no '=' escaping in the extension fields. The following:

CEF:0|security|threatmanager|1.0|100|detected a = in message|10|src=10.0.0.1 act=blocked a \\= dst=1.1.1.1 

produces the fields:

  "fields": {
    "src": "10.0.0.1",
    "act": "blocked a",
    "\\": "",
    "dst": "1.1.1.1"
  },

When it should, I think, produce:

  "fields": {
    "src": "10.0.0.1",
    "act": "blocked a \\",
    "dst": "1.1.1.1"
  },
hanvyj pushed a commit to hanvyj/nsyslog-parser that referenced this issue Sep 25, 2020
@hanvyj hanvyj closed this as completed Sep 9, 2024
@hanvyj hanvyj reopened this Sep 9, 2024
@solzimer
Copy link
Owner

Hi @hanvyj sorry for being soooo late reviewing this. Let me take a look and i will merge the changes. Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants