GHSA-jr66-9ghf-6gp3 CVE-2023-3192
Froxlor Session Fixation vulnerability
- Severity
- 5.4 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.43%
- Chance of exploitation in the next 30 days. Higher than 37.38% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-384 Session Fixation
- Fix
2.1.0- Upgrade froxlor/froxlor to this version or later
Description
Versions of froxlor/froxlor prior to release 2.1.0 did not regenerate session ids appropriately which may result in session fixation.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| froxlor/froxlor | < 2.1.0 |
2.1.0 |
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.1.0
- composer
composer require froxlor/froxlor:^2.1.0
Severity breakdown
CVSS 3.1 5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
Weakness
CWE-384: Session Fixation
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
How to prevent it
- Architecture and Design: Invalidate any existing session identifiers prior to authorizing a new user session.
- Architecture and Design: For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
- Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
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