CVE-2017-20178
No exploitation reported by the sources we read.
- Published2023-02-21
- Fixed in2.8.1
- WeaknessCWE-200
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Codiad 2.8.0. It has been rated as problematic. Affected by this issue is the function saveJSON of the file components/install/process.php. The manipulation of the argument data leads to information disclosure. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. Upgrading to version 2.8.1 is able to address this issue. The patch is identified as 517119de673e62547ee472a730be0604f44342b5. It is recommended to upgrade the affected component. VDB-221498 is the identifier assigned to this vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Timeline
dates in UTC- 2023-02-2118:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-11-04 09:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-20178?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-20178?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.8 | < 2.8.1 | 2.8.1 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.8 | = 2.8.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update codiad/codiad to 2.8.1
Advisories and patches
- github.comPatch
- github.comPatch
- github.comRelease Notes
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
- Metasploit modules
- none listed Metasploit Framework
Sources
- CNACVSS 3.13.1known since 2026-10-23
- NVDCVSS 3.17.5read 2026-10-23
- CNACVSS 2.02.1known since 2026-10-23
- CNAweakness (CWE)CWE-200known since 2026-10-23
- FIRST EPSSEPSS score0.7 %2026-11-03
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2023-03-03
Identifiers
- EUVD-2023-0602same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-2q79-56rq-8v3csame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2023-02-21
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-2q79-56rq-8v3c
Frequently asked questions
What is CVE-2017-20178?
Is CVE-2017-20178 actively exploited?
What is the CVSS score for CVE-2017-20178?
Running codiad/codiad? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-2q79-56rq-8v3c
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served