GHSA-cp68-42pf-6627 CVE-2023-0315
Froxlor vulnerable to Command Injection
High
Packagist
- Severity
- 8.8 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 97.65%
- Chance of exploitation in the next 30 days. Higher than 99.90% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
- Fix
2.0.8- Upgrade froxlor/froxlor to this version or later
Description
Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| froxlor/froxlor | < 2.0.8 |
2.0.8 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
froxlor/froxlor Packagist → 2.0.8
- composer
composer require froxlor/froxlor:^2.0.8
Severity breakdown
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How to prevent it
- Architecture and Design: If at all possible, use library calls rather than external processes to recreate the desired functionality.
- Implementation: If possible, ensure that all external commands called from the program are statically created.
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- Operation: Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
- System Configuration: Assign permissions that prevent the user from accessing/opening privileged files.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-7788-ghfq-c6mh Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints | Critical | Also affects froxlor/froxlor |
| GHSA-xpr4-8vp6-c87j Froxlor has CSRF Vulnerability in AJAX Endpoint — Missing Cross-Site Request Forgery Protection | Medium | Also affects froxlor/froxlor |
| GHSA-5rw4-4665-cvwf Froxlor DomainZones.add allows DNS zone-file RR injection via record/type fields | Medium | Also affects froxlor/froxlor |
| GHSA-w27m-rmmf-g5w4 Froxlor: Second-Order SQL Injection via `Admins.add` `ipaddress` Parameter Allows Full Database Exfiltration | High | Also affects froxlor/froxlor |
| GHSA-43gm-9rr3-cx7g Froxlor: Stored XSS in DNS TXT Record Content Allows Customer-to-Admin Account Takeover | High | Also affects froxlor/froxlor |
| GHSA-q4rm-m6xh-5pv7 Froxlor customer can create MySQL databases on disallowed servers via Mysqls.add API | Medium | Also affects froxlor/froxlor |
| GHSA-mr9h-45p9-fg8h Froxlor: Authenticated customers can read other customers' allowed sender aliases | Medium | Also affects froxlor/froxlor |
| GHSA-f9rx-7wf7-jr36 Froxlor's API Authentication bypasses 2FA Authentication | High | Also affects froxlor/froxlor |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor