| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Postboard 2.0/2.0.1. Affected is an unknown function of the component Code Tag Handler. This manipulation with the input $software_input_value causes resource consumption.
The identification of this vulnerability is CVE-2002-0534. There is no exploit available.
Details
A vulnerability has been found in Postboard 2.0/2.0.1 (Forum Software) and classified as problematic. Affected by this vulnerability is an unknown code of the component Code Tag Handler. The manipulation with the input value \0 leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
PostBoard 2.0.1 and earlier with BBcode allows remote attackers to cause a denial of service (CPU consumption) and corrupt the database via null \0 characters within [code] tags.
The weakness was shared 08/12/2002 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2002-0534. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 10607 (PostBoard BBCode Denial of Service Vulnerability).
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 databases at X-Force (8883), SecurityFocus (BID 4562†) and Vulnerability Center (SBV-6402†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
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: Resource consumptionCWE: CWE-400 / CWE-404
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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/19/2002 🔍08/12/2002 🔍
08/12/2002 🔍
08/12/2002 🔍
12/12/2004 🔍
07/22/2014 🔍
09/16/2025 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2002-0534 (🔍)
GCVE (CVE): GCVE-0-2002-0534
GCVE (VulDB): GCVE-100-18589
X-Force: 8883
SecurityFocus: 4562 - PostBoard BBCode Denial Of Service Vulnerability
Vulnerability Center: 6402 - DoS in PostBoard 2.0, 2.0.1 via [code] Tags, Medium
Entry
Created: 07/22/2014 22:30Updated: 09/16/2025 13:13
Changes: 07/22/2014 22:30 (53), 05/27/2019 09:28 (3), 09/16/2025 13:13 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.