Tag
#git
A new set of malicious packages has been unearthed in the Python Package Index (PyPI) repository that masqueraded as cryptocurrency wallet recovery and management services, only to siphon sensitive data and facilitate the theft of valuable digital assets. "The attack targeted users of Atomic, Trust Wallet, Metamask, Ronin, TronLink, Exodus, and other prominent wallets in the crypto ecosystem,"
### Impact When using `tonic::transport::Server` there is a remote DoS attack that can cause the server to exit cleanly on accepting a tcp/tls stream. This can be triggered via causing the accept call to error out with errors there were not covered correctly causing the accept loop to exit. More information can be found [here](https://github.com/hyperium/tonic/issues/1897) ### Patches Upgrading to tonic `0.12.3` and above contains the fix. ### Workarounds A custom accept loop is a possible workaround.
### Summary Stored Cross-Site Scripting (XSS) can archive via Uploading a new Background for a Custom Map. ### Details Users with "admin" role can set background for a custom map, this allow the upload of SVG file that can contain XSS payload which will trigger onload. This led to Stored Cross-Site Scripting (XSS). ### PoC 1. Login using an Admin role account. 2. Go over to "$URL/maps/custom", the Manage Custom Maps. ![image](https://github.com/user-attachments/assets/9d621532-7880-4010-b12d-efd377f0cfdd) 3. Create a new map then choose to edit it. 4. Choose the "Set Background" option. ![image](https://github.com/user-attachments/assets/dc2e9453-ef3e-4649-a42f-60b7a2ad8189) 5. Choose to upload a SVG file that have this content. ```svg <svg xmlns="http://www.w3.org/2000/svg" onload="alert(document.domain)"> <circle cx="50" cy="50" r="40" /> </svg> ``` 6. Once uploaded, there should be a link to the SVG return in the POST request to the API "$URL/maps/custom/1/background". ![ima...
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.
Next time you need to activate a subscription on your TV, watch out for these fake sites scammers are using to trick you and steal your money.
### Summary A Stored Cross-Site Scripting (XSS) vulnerability in the "Alert Transports" feature allows authenticated users to inject arbitrary JavaScript through the "Details" section (which contains multiple fields depending on which transport is selected at that moment). This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions. ### Details The vulnerability occurs when creating an alert transport. The application does not properly sanitize the user input in the "Details" field, allowing an attacker to inject and store arbitrary JavaScript. This script is then executed in the context of the page whenever the alert transport is viewed or processed. For instance, the following payload can be used to trigger the XSS: ```test1<script>{onerror=alert}throw 1337</script>``` When the page containing the transport details is loaded, this payload causes the browser to exec...
### Summary The application fail to sanitising inputs properly and rendering the code from user input to browser which allow an attacker to execute malicious javascript code. ### Details User with Admin role can create a Device Groups, the application did not properly sanitize the user input in the Device Groups name, when user see the detail of the Device Group, if java script code is inside the name of the Device Groups, its will be trigger. ### PoC 1. Login as an Admin role user. Then go over to "$URL/device-groups" 2. Create a new Device Group with this payload in their name ```js <img src="x" onerror="alert(document.cookie)"> ``` ![image](https://github.com/user-attachments/assets/2764b313-ee65-47e9-ab57-559d75f4575c) 3. Go over to the detail page of that Device Groups, in this case "$URL/devices/group=2". Will see a pop-up. ![image](https://github.com/user-attachments/assets/f743ca74-5dcb-4e72-ac56-dda2b42e2986) ### Impact Attacker can use this to perform malicious java scri...