[pull] main from VirusTotal:main - #281
Open
pull[bot] wants to merge 9 commits into
Open
Conversation
If the `stderr-logs` feature is enabled the YARA-X library emits log messages to stderr. The CLI now uses the same feature for enabling logs instead of using `logging`.
#717) Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.2 to 3.1.4. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.2...v3.1.4) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…nner.MaxMatchedPerPattern` to the Go API.
…e to the project. Closes #721.
Improvements in LNK module: - parse Shell Items - parse sections in LNK files with invalid section sizes (abused by CVE-2010-2568 exploits) --- The Windows Shell Item format isn't officially standardized by Microsoft and therefore community-made documents are the best available source of truth: - [libfwsi](https://github.com/libyal/libfwsi/blob/main/documentation/Windows%20Shell%20Item%20format.asciidoc) - [LnkParse3](https://github.com/Matmaus/LnkParse3/tree/master) - referenced by @plusvic in the TODO comment. Shell item types differ in their internal structure while some parts of them are not fully understood but some of them contain encoded valuable data (filepaths, URLs, which are usually UTF-16 encoded) that could have their own field in the lnk module proto output to improve user experience. I would like to open a discussion especially about the output of the LNK module regarding the shell items: - which shell item types should we recognize - which fields of a certain shell item type could we expose in LNK proto and how to include them there I have implemented yet parsing of some basic shell item types and exposed the most valuable fields in the proto. --------- Co-authored-by: Victor M. Alvarez <vmalvarez@virustotal.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )