CVE-2022-28171: The web module in some Hikvision Hybrid SAN/Cluster Storage products have the following security vulnerability.
Noroxi assessment
Priority: Plan (action score 54/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 51.6% (FIRST EPSS); higher than 98.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 9.8.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The web module in some Hikvision Hybrid SAN/Cluster Storage products have the following security vulnerability. Due to the insufficient input validation, attacker can exploit the vulnerability to execute restricted commands by sending messages with malicious commands to the affected device.
- Published
- Jun 27, 2022
- Updated
- Jun 17, 2026
- EPSS
- 51.6% · 98th percentile
- CWE
- CWE-78
Report tools
Action score
54
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 15 / 30 · 51.6%
CNA vs NVD score
- NVD
- 9.8
- CNA · hikvision
- 7.5
- 2.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hikvision | ds-a71024 firmware | cpe:2.3:o:hikvision:ds-a71024_firmware |
| hikvision | ds-a71024 | cpe:2.3:h:hikvision:ds-a71024 |
| hikvision | ds-a71048 firmware | cpe:2.3:o:hikvision:ds-a71048_firmware |
| hikvision | ds-a71048 | cpe:2.3:h:hikvision:ds-a71048 |
| hikvision | ds-a71072r firmware | cpe:2.3:o:hikvision:ds-a71072r_firmware |
| hikvision | ds-a71072r | cpe:2.3:h:hikvision:ds-a71072r |
| hikvision | ds-a80624s firmware | cpe:2.3:o:hikvision:ds-a80624s_firmware |
| hikvision | ds-a80624s | cpe:2.3:h:hikvision:ds-a80624s |
| hikvision | ds-a81016s firmware | cpe:2.3:o:hikvision:ds-a81016s_firmware |
| hikvision | ds-a81016s | cpe:2.3:h:hikvision:ds-a81016s |
| hikvision | ds-a72024 firmware | cpe:2.3:o:hikvision:ds-a72024_firmware |
| hikvision | ds-a72024 | cpe:2.3:h:hikvision:ds-a72024 |
and 10 more
Using ds-a71024 firmware? Add it to your stack and be the first to know about CVEs like this one. (IP camera)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hikvision ds-a71024 firmwareup to 2.3.8-6 inclusive
- hikvision ds-a71024 firmwareup to 1.1.4 inclusive
- hikvision ds-a71048 firmwareup to 2.3.8-6 inclusive
- hikvision ds-a71048r-cvs firmwareup to 1.1.4 inclusive
- hikvision ds-a71072r firmwareup to 2.3.8-6 inclusive
- hikvision ds-a72024 firmwareup to 1.1.4 inclusive
- hikvision ds-a72024 firmwareup to 2.3.8-6 inclusive
- hikvision ds-a72048r-cvs firmwareup to 1.1.4 inclusive
- hikvision ds-a72072r firmwareup to 2.3.8-6 inclusive
- hikvision ds-a80316s firmwareup to 2.3.8-6 inclusive
- hikvision ds-a80624s firmwareup to 2.3.8-6 inclusive
- hikvision ds-a81016s firmwareup to 2.3.8-6 inclusive
- hikvision ds-a82024d firmwareup to 2.3.8-6 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hikvision). Independent of NVD's CPE analysis and usually ahead of it.
hikvision DS-A71024/48/72R,DS-A80624S,DS-A81016S,DS-A72024/72R,DS-A80316S,DS-A82024D
- V2.X and later · up to and including V2.3.8-6affected
hikvision DS-A71024/48R-CVS,DS-A72024/48R-CVS
- V1.X and later · up to and including V1.1.4affected
Same product
hikvision: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-28808Some Hikvision Hybrid SAN/Cluster Storage products have an access control vulnerability which can be used to obtain the admin permission.39Monitor
- CVE-2022-28172The web module in some Hikvision Hybrid SAN/Cluster Storage products have the following security vulnerability.24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×2
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2023-07-19 |
| Proof-of-concept repository on GitHub | stars:4 | 2023-07-16 |
| Proof-of-concept repository on GitHub | stars:3 | 2024-11-26 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+383 d
- TodayNov 4, 2026+1591 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.