fossbilling up to 0.4.x insufficient granularity of access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in fossbilling up to 0.4.x. The impacted element is an unknown function. Performing a manipulation results in insufficient granularity of access control. This vulnerability was named CVE-2023-3227. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in fossbilling up to 0.4.x (Billing Software). It has been classified as critical. This affects some unknown functionality. The manipulation with an unknown input leads to a insufficient granularity of access control vulnerability. CWE is classifying the issue as CWE-1220. The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Insufficient Granularity of Access Control in GitHub repository fossbilling/fossbilling prior to 0.5.0.
The weakness was presented 06/14/2023. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2023-3227 since 06/14/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.5.0 eliminates this vulnerability. Applying the patch b65a75fcf70feaf547d414672f78d7cbe8a98e7e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-43903). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (huntr.dev): 🔍
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: Insufficient granularity of access controlCWE: CWE-1220 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: fossbilling 0.5.0
Patch: b65a75fcf70feaf547d414672f78d7cbe8a98e7e
Timeline
06/14/2023 🔍06/14/2023 🔍
06/14/2023 🔍
01/26/2026 🔍
Sources
Product: github.comAdvisory: b65a75fcf70feaf547d414672f78d7cbe8a98e7e
Status: Confirmed
CVE: CVE-2023-3227 (🔍)
GCVE (CVE): GCVE-0-2023-3227
GCVE (VulDB): GCVE-100-231513
EUVD: 🔍
Entry
Created: 06/14/2023 09:21Updated: 01/26/2026 19:40
Changes: 06/14/2023 09:21 (50), 07/13/2023 10:07 (1), 01/26/2026 19:40 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.