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

File created whitelist editor interface not working #79

Open
sebastiendamaye opened this issue Dec 21, 2020 · 4 comments
Open

File created whitelist editor interface not working #79

sebastiendamaye opened this issue Dec 21, 2020 · 4 comments

Comments

@sebastiendamaye
Copy link

The "File created whitelist editor" view (file_create_whitelist.xml) doesn't work. Clicking on the "Submit" button doesn't add the entry, and the csv file threathunting_file_create_whitelist.csv should be manually edited.

@sebastiendamaye
Copy link
Author

sebastiendamaye commented Dec 27, 2020

Patch to apply to default/data/ui/views/file_create_whitelist.xml to fix the issue:

@@ -48,6 +48,7 @@
         <title>Today's Entries</title>
         <search>
           <query>| makeresults 
+| eval input_host_fqdn = COALESCE(if(trim("$host_fqdn$")="", "*", trim("$host_fqdn$")), "*") 
 | eval input_mitre_technique_id = COALESCE(if(trim("$mitre_technique_id$")="", "*", trim("$mitre_technique_id$")), "*") 
 | eval input_process_path = COALESCE(if(trim("$process_path$")="", "*", trim("$process_path$")), "*") 
 | eval input_file_name = COALESCE(if(trim("$file_name$")="", "*", trim("$file_name$")), "*") 

@Suirand1
Copy link

Suirand1 commented Mar 18, 2021

@sebastiendamaye your patch does not work for me.
Adding | eval input_host_fqdn = COALESCE(if(trim("$host_fqdn$")="", "*", trim("$host_fqdn$")), "*") did not fix issue for newest version of threathunting app.
Pressing submit button deletes first line of my lookup CSV file

@sebastiendamaye
Copy link
Author

@Suirand1 I applied the patch on the latest release (1.4.92) and it's working fine. Just make sure you restart Splunk once you have applied the patch.

screenshot

@sebastiendamaye
Copy link
Author

@olafhartong I take this opportunity to confirm that the latest release (1.4.92) is still suffering from this bug :)

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