1c:I[41658,["67895","static/chunks/67895-7befafdccbc48894.js","51219","static/chunks/51219-5620f8acea6536a8.js","40430","static/chunks/40430-9b4d144f4e63e85b.js","27501","static/chunks/27501-b81020cf9f612c88.js","85405","static/chunks/85405-4629db2ab7d80b03.js","16725","static/chunks/16725-c775e512206b762d.js","11272","static/chunks/11272-5cb5a9c0e51c3cac.js","28860","static/chunks/28860-473b689f2c736e27.js","11621","static/chunks/11621-dab816603cd195b7.js","17190","static/chunks/17190-6f2912f2e8e93809.js","83799","static/chunks/83799-75b851029f8ead66.js","22594","static/chunks/22594-b6e9d17969c7b505.js","91009","static/chunks/91009-2606db4f83830b09.js","14825","static/chunks/14825-4b92e7fb615135c7.js","91251","static/chunks/91251-342071341969cc75.js","85539","static/chunks/85539-57c4de78f1bfdd64.js","80193","static/chunks/80193-da6cf98bc1776c93.js","2113","static/chunks/2113-a480c8ea27d2617f.js","56007","static/chunks/56007-469ec3cc943d6cb6.js","91014","static/chunks/app/(public)/action-advisor/%5B...action%5D/page-eccc797302add311.js"],"ActionAdvisorScorecardClient",1] 1d:T4a8,Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.1e:T48e,Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc. Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.1f:T48e,Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption. Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 f

	snyk/actions/gradle-8-jdk21
Score	Start free trial to unlock No credit card required
License
Maintained
Vulnerabilities
Docker vulnerabilities
Branch protection
Manual code review
Secure publishing
Signed commits
Automated security tools
Popular	Used by 2 open-source projects
Security Policy	security policy file detected

snyk/actions/gradle-8-jdk21