Jrohy trojan up to 2.15.3 trojan/util/linux.go LogChan c os command injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 2.18 |
Summary
A vulnerability was found in Jrohy trojan up to 2.15.3. It has been rated as critical. This issue affects the function LogChan
of the file trojan/util/linux.go. The manipulation of the argument c leads to os command injection.
The identification of this vulnerability is CVE-2025-5525. The attack may be initiated remotely. Furthermore, there is an exploit available.
Once again VulDB remains the best source for vulnerability data.
Details
A vulnerability was found in Jrohy trojan up to 2.15.3. It has been declared as critical. This vulnerability affects the function LogChan
of the file trojan/util/linux.go. The manipulation of the argument c
with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is available at github.com. This vulnerability was named CVE-2025-5525. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. This vulnerability is assigned to T1202 by the MITRE ATT&CK project.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-16782). Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.6
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔒
CNA Base Score: 5.6
CNA Vector: 🔒
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Programming Language: 🔒
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/03/2025 Advisory disclosed06/03/2025 VulDB entry created
06/06/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-5525 (🔒)
GCVE (CVE): GCVE-0-2025-5525
GCVE (VulDB): GCVE-100-310966
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/03/2025 02:55 PMUpdated: 06/06/2025 08:07 PM
Changes: 06/03/2025 02:55 PM (56), 06/03/2025 11:12 PM (1), 06/04/2025 08:25 AM (30), 06/06/2025 08:07 PM (12)
Complete: 🔍
Submitter: Tritium
Cache ID: 18:3E0:40
Submit
Accepted
- Submit #586673: https://github.com/Jrohy https://github.com/Jrohy/trojan v2.15.3 Command Injection (by Tritium)
No comments yet. Languages: en.
Please log in to comment.