-
Notifications
You must be signed in to change notification settings - Fork 425
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
False Positives in Safe PDF File Analysis #2086
Comments
Those are community signatures, you are welcome to improve them
El vie, 26 abr 2024, 12:07, XxCloudMindXx ***@***.***>
escribió:
… Expected Behavior:
- The system should accurately analyze safe PDF files without
triggering false positive alerts, score should not be 10/10.
Current Behavior:
- The system is showing numerous false positives during the analysis
of safe PDF files. These false positives include:
Signatures:
Possible Heap Spray Exploit Detection:
Time: 2024-04-17 09:01:09
Caller: 0x7793553c
API: NtAllocateVirtualMemory
Arguments: ProcessHandle: 0xffffffffffffffff, BaseAddress: 0x00dd1000, RegionSize: 0x00001000, Protection: PAGE_READWRITE
Status: Success
Return: 0x00000000
[Additional similar instances...]
Collects and Encrypts Information:
Time: 2024-04-17 09:01:36
Caller: 0x008e7de7
API: CryptHashData
Arguments: CryptHash: 0x014ed7d8, Buffer: [Encrypted Data]
Status: Success
Return: 0x00000001
[Additional similar instances...]
Attempted Loading of File with Unusual Extension as DLL:
Time: 2024-04-17 09:01:14
Caller: 0x0050005c
API: LdrLoadDll
Arguments: Flags: 0x00000000, FileName: C:\program files (x86)\Adobe\Reader 9.0\Reader\RdLang32.FRA, BaseAddress: 0x00000000
Status: Success
Return: 0x00000000
[Additional similar instances...]
CAPE Extracted Potentially Suspicious Content:
Suspicious Content: AcroRd32_exe: embedded_pe
Display of Potential Decoy Document to User:
Decoy Document: "c:\program files (x86)\adobe\reader 9.0\reader\acrord32.exe" "c:\users\admin\appdata\local\temp\safe.pdf"
Time: 2024-04-17 09:01:09
Caller: 0x77941e7e
API: NtDelayExecution
Arguments: Milliseconds: 30, Status: Skipped
Creation of Hidden or System Files:
Files: C:\ProgramData\Adobe\Reader\9.2\ARM\BITAF7C.tmp, C:\ProgramData\Adobe\Reader\9.2\ARM\BITE84F.tmp
[Details of NtCreateFile calls...]
Access to Credential Storage Registry Keys:
Registry Key: HKEY_LOCAL_MACHINE\System
System Fingerprinting Information Collection:
Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Registration\ProductId
Yara Detections:
Yara Rule: embedded_pe
Process ID: 4272
Steps to Reproduce:
Submit a safe PDF file for analysis.
Observe the generated alerts and false positives.
Additional Information:
- Operating System: Win 10 Pro
- CAPEV2 Version: [17.11.2023]
- Adobe Reader : 9.0
- File Type PDF document, version 1.3
- PDF Information:
Keyword Count
obj 329
endobj 329
stream 99
endstream 91
xref 1
trailer 1
startxref 1
/Page 38
/Encrypt 0
/ObjStm 0
/JS 0
/JavaScript 0
/AA 0
/OpenAction 0
/AcroForm 0
/JBIG2Decode 0
/RichMedia 0
/Launch 0
/EmbeddedFile 0
/XFA 0
/Colors > 2^24 0
—
Reply to this email directly, view it on GitHub
<#2086>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOFH37BPMAQ26HIQM4FWXLY7IRPLAVCNFSM6AAAAABG2PYYUOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI3DKNBUGUYDINI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Which score are you referring to? If it's malscore, this is a legacy cuckoo feature which is not enabled in CAPE by default for exactly this reason. The difficulty is in how to avoid scoring actions like these but still catch malicious actions that use the same or similar API. I would be interested to hear any proposal to solve this problem - failing that as I mentioned this is exactly why malscore is not enabled by default. My advice would be to disable it. |
@kevoreilly I suggest to fix [Accessed credential storage registry keys] while analysing pdf using adobe reader is to reduce the severity using
And also i created a new pdf annot url checker because the https://github.com/CAPESandbox/community/blob/master/modules/signatures/all/pdf_annot_urls.py not working anymore
And a malicious/suspect tld in /opt/CAPEv2/data/malicioustlds.txt
The new script is working well with dyanmic and static scan (tested in Win10 and adobe reader 9) |
Sometimes CAPE suricata Alert trigger "AKAMAI-AS" as malicious severity 3, i suggest also to add commenting |
@wasbt thank you for your suggestions - I have created a PR with these changes as I am very keen to welcome contributions. We would however appreciate PRs in future as it saves unnecessary effort. |
Expected Behavior:
Current Behavior:
Signatures:
Steps to Reproduce:
Additional Information:
The text was updated successfully, but these errors were encountered: