Kanboard up to 1.0.46 Form Data information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Kanboard up to 1.0.46. Affected by this issue is some unknown functionality of the component Form Data Handler. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2017-15212. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Kanboard up to 1.0.46 (Forum Software). This issue affects some unknown functionality of the component Form Data Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In Kanboard before 1.0.47, by altering form data, an authenticated user can at least see the names of tags of a private project of another user.
The bug was discovered 10/04/2017. The weakness was shared 10/11/2017 (Website). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2017-15212 since 10/10/2017. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 1.0.47 eliminates this vulnerability.
The entries VDB-107652, VDB-107653, VDB-107654 and VDB-107655 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
- 1.0.6
- 1.0.7
- 1.0.8
- 1.0.9
- 1.0.10
- 1.0.11
- 1.0.12
- 1.0.13
- 1.0.14
- 1.0.15
- 1.0.16
- 1.0.17
- 1.0.18
- 1.0.19
- 1.0.20
- 1.0.21
- 1.0.22
- 1.0.23
- 1.0.24
- 1.0.25
- 1.0.26
- 1.0.27
- 1.0.28
- 1.0.29
- 1.0.30
- 1.0.31
- 1.0.32
- 1.0.33
- 1.0.34
- 1.0.35
- 1.0.36
- 1.0.37
- 1.0.38
- 1.0.39
- 1.0.40
- 1.0.41
- 1.0.42
- 1.0.43
- 1.0.44
- 1.0.45
- 1.0.46
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
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: Information disclosureCWE: CWE-200 / 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: Kanboard 1.0.47
Patch: github.com
Timeline
10/04/2017 🔍10/10/2017 🔍
10/10/2017 🔍
10/11/2017 🔍
10/11/2017 🔍
01/03/2023 🔍
Sources
Product: github.comAdvisory: 074f6c104f3e49401ef0065540338fc2d4be79f0
Status: Not defined
CVE: CVE-2017-15212 (🔍)
GCVE (CVE): GCVE-0-2017-15212
GCVE (VulDB): GCVE-100-107669
See also: 🔍
Entry
Created: 10/11/2017 09:54Updated: 01/03/2023 09:46
Changes: 10/11/2017 09:54 (59), 11/23/2019 13:37 (1), 01/03/2023 09:46 (5)
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.