Netbox 4.0.3 /dcim/power-ports/add/ Name cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Netbox 4.0.3. It has been rated as problematic. This affects an unknown function of the file /dcim/power-ports/add/. This manipulation of the argument Name causes cross site scripting. The identification of this vulnerability is CVE-2024-38972. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in Netbox 4.0.3 and classified as problematic. Affected by this vulnerability is an unknown function of the file /dcim/power-ports/add/. The manipulation of the argument Name with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:
A cross-site scripting (XSS) vulnerability in netbox v4.0.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Name parameter at /dcim/power-ports/add/.
The advisory is shared at github.com. This vulnerability is known as CVE-2024-38972 since 06/21/2024. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 206 days. During that time the estimated underground price was around .
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CNA Base Score: 6.1
CNA Vector (MITRE): 🔍
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: 🔍
Timeline
12/01/2023 🔍06/21/2024 🔍
06/24/2024 🔍
07/09/2024 🔍
07/09/2024 🔍
03/19/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2024-38972 (🔍)
GCVE (CVE): GCVE-0-2024-38972
GCVE (VulDB): GCVE-100-270949
Entry
Created: 07/09/2024 23:15Updated: 03/19/2025 19:26
Changes: 07/09/2024 23:15 (53), 07/10/2024 18:18 (3), 07/10/2024 18:22 (5), 07/11/2024 06:43 (12), 07/12/2024 15:02 (11), 03/19/2025 19:26 (4)
Complete: 🔍
Committer: Anonymous User
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
You opened up (spammed) VulDB for the same vulnerability (on a single page /cables/) the link between ports (power port, interfaces, front ports, rear ports, power outlets, console cables, console ports, power feeds, circuits, etc) is incorrectly sanitized. In the same vein, both /add and /edit are the same form, just with data pre-filled or missing. This is at best 1 vulnerability, not 17+ since the actual issue can only be presented in 1 area.
You did not follow the proper vulnerability disclosure process (opening a vulnerability report on github) and as such did not read our security.md file.
Do you need the next level of professionalism?
Upgrade your account now!