Event ID 11 - Empty TargetFilename
@MarioHewardt ci sta già lavorando.
Dal 23/10/2023.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Describe the bug
All events ID 11 - File Create are missing values in TargetFilename field. Only dash (-) is being shown.
Works OK for event ID 23 - File Delete - path and filename is present.
To Reproduce
Happened with both default config ("catch all" and custom configs)
Sysmon version
Tested on both 1.3.0 and newest 1.3.1
Distro/kernel version
Linux xxx 5.4.0-72-generic #80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 20.04LTS
Sysmon configuration
Tested with default catch all config. Tested this one: https://github.com/microsoft/MSTIC-Sysmon/blob/main/linux/configs/main.xml and tested couple of custom configurations, all with same results - events are being collected but TargetFilename field is empty.
Logs
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:58:58.151
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:58:58.151
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:09.978
ProcessGuid: {c8ee428b-43e2-6536-15b6-ced6bf550000}
ProcessId: 3045565
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:09.978
User: isd_poc_security
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:14.168
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:14.168
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:21.021
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:21.021
User: -
Event SYSMONEVENT_FILE_CREATE
RuleName: TechniqueID=T1546,TechniqueName=Event Trigerred Execution
UtcTime: 2023-10-23 09:59:21.030
ProcessGuid: {c8ee428b-43f2-6536-15b6-41abbf550000}
ProcessId: 3045567
Image: /usr/bin/vim.basic
TargetFilename: -
CreationUtcTime: 2023-10-23 09:59:21.030
User: -
Expected behavior
A path and file name is expected in TargetFilename same way as for ID 23 file delete. Without this information it is not possible to investigate events and perform filtering in config file.
Thank you.
Regards,
Jozef
- Lingua principale
- C
- Stelle
- 2.2k
- Fork
- 220
- Merge medio
- 11g 22h
- PR unite (30g)
- 2
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/SysmonForLinux
-
microsoft/SysmonForLinux#238 · 1 assegnatario ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
microsoft/SysmonForLinux#233 ·
-
microsoft/SysmonForLinux#230 · 1 assegnatario ·
-
microsoft/SysmonForLinux#226 · 1 assegnatario ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
microsoft/SysmonForLinux#220 · 2 reazioni ·
Tutte le issue di microsoft/SysmonForLinux
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
zephyrproject-rtos/zephyr#119726 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
api7/lua-resty-saml#63 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
BasedHardware/omi#15320 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 commenti ·