Backstage up to 0.3.74 Environment Variable APP_CONFIG_backend_listen_port expected behavior violation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Backstage up to 0.3.74. This vulnerability affects unknown code of the component Environment Variable Handler. The manipulation of the argument APP_CONFIG_backend_listen_port leads to expected behavior violation. This vulnerability is documented as CVE-2024-47762. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Backstage up to 0.3.74. It has been rated as problematic. This issue affects an unknown functionality of the component Environment Variable Handler. The manipulation of the argument APP_CONFIG_backend_listen_port with an unknown input leads to a expected behavior violation vulnerability. Using CWE to declare the problem leads to CWE-440. A feature, API, or function does not perform according to its specification. Impacted is confidentiality. The summary by CVE is:
Backstage is an open framework for building developer portals. Configuration supplied through APP_CONFIG_* environment variables, for example APP_CONFIG_backend_listen_port=7007, where unexpectedly ignoring the visibility defined in configuration schema. This occurred even if the configuration schema specified that they should have backend or secret visibility. This was an intended feature of the APP_CONFIG_* way of supplying configuration, but now clearly goes against the expected behavior of the configuration system. This behavior leads to a risk of potentially exposing sensitive configuration details intended to remain private or restricted to backend processes. The issue has been resolved in version 0.3.75 of the @backstage/plugin-app-backend package. As a temporary measure, avoid supplying secrets using the APP_CONFIG_ configuration pattern. Consider alternative methods for setting secrets, such as the environment substitution available for Backstage configuration.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-47762 since 09/30/2024. 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.
Upgrading to version 0.3.75 eliminates this vulnerability. Applying the patch 323e6129073c5cb4cc106a1239eaec31a129554f 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.3.0
- 0.3.1
- 0.3.2
- 0.3.3
- 0.3.4
- 0.3.5
- 0.3.6
- 0.3.7
- 0.3.8
- 0.3.9
- 0.3.10
- 0.3.11
- 0.3.12
- 0.3.13
- 0.3.14
- 0.3.15
- 0.3.16
- 0.3.17
- 0.3.18
- 0.3.19
- 0.3.20
- 0.3.21
- 0.3.22
- 0.3.23
- 0.3.24
- 0.3.25
- 0.3.26
- 0.3.27
- 0.3.28
- 0.3.29
- 0.3.30
- 0.3.31
- 0.3.32
- 0.3.33
- 0.3.34
- 0.3.35
- 0.3.36
- 0.3.37
- 0.3.38
- 0.3.39
- 0.3.40
- 0.3.41
- 0.3.42
- 0.3.43
- 0.3.44
- 0.3.45
- 0.3.46
- 0.3.47
- 0.3.48
- 0.3.49
- 0.3.50
- 0.3.51
- 0.3.52
- 0.3.53
- 0.3.54
- 0.3.55
- 0.3.56
- 0.3.57
- 0.3.58
- 0.3.59
- 0.3.60
- 0.3.61
- 0.3.62
- 0.3.63
- 0.3.64
- 0.3.65
- 0.3.66
- 0.3.67
- 0.3.68
- 0.3.69
- 0.3.70
- 0.3.71
- 0.3.72
- 0.3.73
- 0.3.74
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.8
CNA Vector (GitHub_M): 🔍
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: Expected behavior violationCWE: CWE-440 / CWE-436
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: Backstage 0.3.75
Patch: 323e6129073c5cb4cc106a1239eaec31a129554f
Timeline
09/30/2024 🔍10/03/2024 🔍
10/03/2024 🔍
10/04/2024 🔍
Sources
Product: github.comAdvisory: GHSA-qc4v-xq2m-65wc
Status: Confirmed
CVE: CVE-2024-47762 (🔍)
GCVE (CVE): GCVE-0-2024-47762
GCVE (VulDB): GCVE-100-279161
Entry
Created: 10/03/2024 21:44Updated: 10/04/2024 12:57
Changes: 10/03/2024 21:44 (66), 10/04/2024 12:57 (1)
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.