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

Proofpoint analyzer fails Unexpected Error: Unicode-objects must be encoded before hashing #162

Closed
blainedw opened this issue Jan 20, 2019 · 11 comments
Labels

Comments

@blainedw
Copy link

Request Type

(select Bug or Feature Request and remove this line)
Bug / Feature Request

Work Environment

RHEL7
Cortex 2.1.3-1
Elastic4Play 1.7.2
Play 2.6.20
Elastic4s 5.6.6
ElasticSearch client 5.6.9
ElasticSearch cluster 5.6.14
IE 11

Problem Description

Proofpoint analyzer fails with Unexpected Error: Unicode-objects must be encoded before hashing.

Steps to Reproduce

Provide url to Proofpoint analyzer and run.

@nadouani
Copy link
Contributor

nadouani commented Feb 5, 2019

Issues related to analyzers should be created in https://github.com/TheHive-Project/Cortex-Analyzers repo

@jeromeleonard
Copy link
Contributor

Hello @blainedw, Could you provide an example of URL to reproduce the issue ?
Thanks.

@blainedw
Copy link
Author

blainedw commented Feb 12, 2019 via email

@saadkadhi
Copy link
Contributor

@blainedw the analyzers and responders enforce the TLP and the PAP. So if you have submitted an observable with a TLP greater than the max one accepted by the analyzer, you'll get that error. This is a safeguard against OPSEC mishaps and mistakes made by analysts who would end up leaking data to an external service if the data should have stayed private in the first place.

@blainedw
Copy link
Author

blainedw commented Feb 12, 2019 via email

@nadouani
Copy link
Contributor

TLP and PAP are not related to the origin of the analyzer issue. Please provide an example to reroduce the problem, otherwise it’s hard to understand what happens :)

@blainedw
Copy link
Author

blainedw commented Feb 15, 2019 via email

@jeromeleonard
Copy link
Contributor

@blainedw could you please copy and paste here the complete report output you can find in Cortex when you click on the "View" button in Jobs history when the analyzer fails ?

Thanks in advance,

@blainedw
Copy link
Author

blainedw commented Feb 20, 2019 via email

@jeromeleonard
Copy link
Contributor

thx.

From what is reported, PAP and TLP checks are enabled and set to AMBER.

Regards,

@blainedw
Copy link
Author

blainedw commented Feb 26, 2019 via email

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

No branches or pull requests

4 participants