Security Advisories
This page lists vulnerability information and security notices related to Kuroco, together with whether Kuroco is affected and the current response status. For details of each advisory, see the linked notice. This page also shows whether Kuroco uses major software for which many vulnerabilities have been reported.
Advisories
You can receive new and updated advisories via RSS. When the status of an advisory is updated, it is delivered as a new item.
For the meaning of each status, see Status definitions. For the meaning of each urgency level, see Urgency criteria. Urgency is shown only for vulnerabilities that may affect Kuroco. In the RSS feed, it is shown at the beginning of the title together with the status. For CVSS, EPSS, and CISA KEV shown in the notices, see Vulnerability metrics.
Usage of major software
This section shows whether Kuroco uses major software for which many vulnerabilities have been reported. For the response status of vulnerabilities in the software that Kuroco uses, see Advisories.
Major software in use
| Software | Usage | Security advisories |
|---|---|---|
| nginx | Used | nginx Security Advisories |
| Envoy | Used | Envoy Security Advisories |
| PHP | Used | PHP Security Advisories |
| PHP-FPM | Used | PHP Security Advisories |
| PostgreSQL | Used | PostgreSQL Security Information Cloud SQL for PostgreSQL maintenance changelog Amazon Aurora PostgreSQL updates |
| Rust | Used | RustSec Advisory Database |
| Go | Used for some features | Go Vulnerability Database |
| Node.js | Used for some features (mainly related to KurocoFront) as a Google Cloud managed service | Node.js Security Releases |
Major software not in use
Kuroco does not use the following software, which we are frequently asked about.
F5 BIG-IP, Fortinet FortiGate (FortiOS), Palo Alto Networks PAN-OS, Ivanti Connect Secure, Citrix NetScaler, Cisco ASA, SonicWall, VMware ESXi / vCenter, Microsoft Exchange Server, Microsoft SharePoint, Windows Server, Apache HTTP Server, Apache Tomcat, Apache Struts, Log4j, Java, Ruby, MongoDB, WordPress, Atlassian Confluence / Jira, MOVEit Transfer, GitLab, OpenSSH
This list does not cover all software. For software not listed here, please contact support.
Status definitions
| Status | Description |
|---|---|
| Investigating | We are investigating whether Kuroco is affected. |
| Affected | We have confirmed that Kuroco is affected and are working on a response. |
| Not affected | We have confirmed that Kuroco is not affected. |
| Resolved | The response on the Kuroco side has been completed. |
| Customer action recommended | We recommend that customers take action in their site settings or implementation. |
Vulnerability metrics
Vulnerability notices show the following publicly available metrics for each CVE. These are general assessments of each CVE and do not indicate whether Kuroco is affected. For the impact on Kuroco, see the response status and the status of each notice.
| Metric | Description | Provider |
|---|---|---|
| CVSS | The base score from 0.0 to 10.0 indicating the severity of the vulnerability. The CVSS version and the organization that assessed it are shown with the score. The CVSS 4.0 score is shown if available; otherwise, the CVSS 3.1 score is shown. Among the assessments published in NVD, those by organizations other than NIST (such as the product vendor) are preferred. | NVD |
| EPSS | The estimated probability that the vulnerability will be exploited within the next 30 days. "-" is shown when no value has been calculated yet, such as for a newly published CVE. | FIRST |
| CISA KEV | Whether the vulnerability is listed in the Known Exploited Vulnerabilities catalog published by the U.S. CISA, which lists vulnerabilities confirmed to be exploited in the wild. | CISA |
CVEs listed in CISA KEV and CVEs with a CVSS base score of 7.0 or higher are shown. CVEs that have not been scored with CVSS are also shown.
The values are as of the retrieval date stated in each notice. Until the response is complete, the values are retrieved again whenever the notice is updated. The values in notices for which the response is complete are not updated. For the latest values, see the link for each CVE.
Urgency criteria
For vulnerabilities that may affect Kuroco, we determine the urgency based on the following criteria and apply a fixed version or mitigation accordingly. Whether Kuroco may be affected is determined by comparing the conditions under which the vulnerability applies with Kuroco's configuration.
| Urgency | Criteria | Applying a fixed version or mitigation (target) |
|---|---|---|
| Critical | Kuroco may be affected, and the vulnerability is listed in CISA KEV or has a CVSS base score of 9.0 or higher | Applied as soon as possible, regardless of holidays or late-night hours (targeting within a few hours). |
| High | Kuroco may be affected, and the vulnerability has a CVSS base score of 7.0 or higher | Applied within one business day. |
| Normal | Kuroco may be affected, and none of the above applies | Applied within a few business days. |
| Not affected | Kuroco is not affected | If a fixed version is available, it is applied within a few business days. |
The times in the table are targets. If what is needed for the application is not available, such as when no fixed version has been released, it may not be possible to apply it within the target time. In that case, we limit the impact with interim measures such as mitigations, and apply the fixed version as soon as it is released.
For business days, see Support hours.
Contact
If you want to check whether Kuroco is affected by a vulnerability that is not listed here, please contact Kuroco support. Requests to check lists of CVEs that you send us periodically are quoted separately. For details, see Can I check whether Kuroco is affected by a specific vulnerability (CVE) or uses specific software?.
Related documents
Support
If you have any other questions, please contact us or check out Our Slack Community.