| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Phorum 3.0.7. It has been classified as problematic. This vulnerability affects unknown code of the file upgrade.php3. The manipulation leads to privileges management. This vulnerability is uniquely identified as CVE-2000-1232. No exploit exists.
Details
A vulnerability was found in Phorum 3.0.7 (Forum Software). It has been rated as problematic. This issue affects an unknown code block of the file upgrade.php3. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is integrity. The summary by CVE is:
upgrade.php3 in Phorum 3.0.7 could allow remote attackers to modify certain Phorum database tables via an unknown method.
The weakness was disclosed 12/31/2000 as not defined posting (Bugtraq). The advisory is shared at cert.uni-stuttgart.de. The identification of this vulnerability is CVE-2000-1232 since 07/14/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-16213, VDB-16214, VDB-16216 and VDB-16218 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/31/2000 🔍12/31/2000 🔍
07/14/2005 🔍
07/02/2014 🔍
05/28/2018 🔍
Sources
Advisory: cert.uni-stuttgart.deStatus: Not defined
CVE: CVE-2000-1232 (🔍)
GCVE (CVE): GCVE-0-2000-1232
GCVE (VulDB): GCVE-100-16217
See also: 🔍
Entry
Created: 07/02/2014 11:47Updated: 05/28/2018 09:20
Changes: 07/02/2014 11:47 (43), 05/28/2018 09:20 (6)
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.