GSD-2023-4485

Vulnerability from gsd - Updated: 2023-12-13 01:20
Details
ARDEREG ​Sistema SCADA Central versions 2.203 and prior login page are vulnerable to an unauthenticated blind SQL injection attack. An attacker could manipulate the application's SQL query logic to extract sensitive information or perform unauthorized actions within the database. In this case, the vulnerability could allow an attacker to execute arbitrary SQL queries through the login page, potentially leading to unauthorized access, data leakage, or even disruption of critical industrial processes.
Aliases
Aliases

{
  "GSD": {
    "alias": "CVE-2023-4485",
    "id": "GSD-2023-4485"
  },
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-4485"
      ],
      "details": "ARDEREG\u00a0\u200bSistema SCADA Central versions 2.203 and prior\nlogin page are vulnerable to an unauthenticated blind SQL injection attack. An attacker could manipulate the application\u0027s SQL query logic to extract sensitive information or perform unauthorized actions within the database. In this case, the vulnerability could allow an attacker to execute arbitrary SQL queries through the login page, potentially leading to unauthorized access, data leakage, or even disruption of critical industrial processes.\n\n",
      "id": "GSD-2023-4485",
      "modified": "2023-12-13T01:20:27.148017Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "ics-cert@hq.dhs.gov",
        "ID": "CVE-2023-4485",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "Sistemas SCADA",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "\u003c=",
                          "version_name": "0",
                          "version_value": "2.203"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "ARDEREG"
            }
          ]
        }
      },
      "credits": [
        {
          "lang": "en",
          "value": "Momen Eldawakhly of Samurai Digital Security Ltd. reported this vulnerability to CISA."
        }
      ],
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "ARDEREG\u00a0\u200bSistema SCADA Central versions 2.203 and prior\nlogin page are vulnerable to an unauthenticated blind SQL injection attack. An attacker could manipulate the application\u0027s SQL query logic to extract sensitive information or perform unauthorized actions within the database. In this case, the vulnerability could allow an attacker to execute arbitrary SQL queries through the login page, potentially leading to unauthorized access, data leakage, or even disruption of critical industrial processes.\n\n"
          }
        ]
      },
      "generator": {
        "engine": "Vulnogram 0.1.0-dev"
      },
      "impact": {
        "cvss": [
          {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          }
        ]
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "cweId": "CWE-89",
                "lang": "eng",
                "value": "CWE-89 SQL Injection"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-243-01",
            "refsource": "MISC",
            "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-243-01"
          }
        ]
      },
      "source": {
        "advisory": "ICSA-23-243-01",
        "discovery": "EXTERNAL"
      },
      "work_around": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\n\n\n\n\u003cp\u003e\u200bARDEREG is aware of the issue. For more information, contact ARDEREG by \u003ca target=\"_blank\" rel=\"nofollow\"\u003eemail\u003c/a\u003e.\u003c/p\u003e\u003cp\u003e\u200bARDEREG recommends the following workarounds to help reduce the risk:\u003c/p\u003e\n\n\u003cul\u003e\u003cli\u003e\u200bSecurity Awareness and Training: Conduct regular security awareness and training sessions for developers, administrators, and other personnel involved in the management and operation of the SCADA system. Educate about the risks and consequences of SQL injection vulnerabilities and provide guidance on secure coding practices, proper input validation, and best practices for securely interacting with databases.\u003c/li\u003e\u003cli\u003e\u200bRegular Security Assessments: Perform regular security assessments, including penetration testing and code reviews, to identify and address any vulnerabilities in the SCADA system. Conduct internal security audits to evaluate the overall security posture and identify any weaknesses an attacker could exploit through SQL injection or other attack vectors.\u003c/li\u003e\u003cli\u003e\u200bIncident Response Plan: Develop and maintain an incident response plan specifically tailored to address security incidents related to SQL injection and other vulnerabilities in the SCADA system. Establish clear procedures and responsibilities for responding to and mitigating security incidents, including containment, investigation, and recovery steps.\u003c/li\u003e\u003cli\u003e\u200bVendor and Supply Chain Security: Ensure the vendors and suppliers involved in the development and maintenance of the SCADA system follow secure coding practices and adhere to strict security standards. Regularly evaluate and monitor the security practices to minimize the risk of introducing vulnerabilities through the supply chain.\u003c/li\u003e\u003cli\u003e\u200bSystem Segmentation: Implement network segmentation to isolate the SCADA system from other less critical systems or public-facing networks. This reduces the attack surface and limits the potential impact of a successful SQL injection attack by containing it within a restricted network segment.\u003c/li\u003e\u003c/ul\u003e\n\n\u003cbr\u003e"
            }
          ],
          "value": "\n\n\n\u200bARDEREG is aware of the issue. For more information, contact ARDEREG by email.\n\n\u200bARDEREG recommends the following workarounds to help reduce the risk:\n\n\n\n  *  \u200bSecurity Awareness and Training: Conduct regular security awareness and training sessions for developers, administrators, and other personnel involved in the management and operation of the SCADA system. Educate about the risks and consequences of SQL injection vulnerabilities and provide guidance on secure coding practices, proper input validation, and best practices for securely interacting with databases.\n  *  \u200bRegular Security Assessments: Perform regular security assessments, including penetration testing and code reviews, to identify and address any vulnerabilities in the SCADA system. Conduct internal security audits to evaluate the overall security posture and identify any weaknesses an attacker could exploit through SQL injection or other attack vectors.\n  *  \u200bIncident Response Plan: Develop and maintain an incident response plan specifically tailored to address security incidents related to SQL injection and other vulnerabilities in the SCADA system. Establish clear procedures and responsibilities for responding to and mitigating security incidents, including containment, investigation, and recovery steps.\n  *  \u200bVendor and Supply Chain Security: Ensure the vendors and suppliers involved in the development and maintenance of the SCADA system follow secure coding practices and adhere to strict security standards. Regularly evaluate and monitor the security practices to minimize the risk of introducing vulnerabilities through the supply chain.\n  *  \u200bSystem Segmentation: Implement network segmentation to isolate the SCADA system from other less critical systems or public-facing networks. This reduces the attack surface and limits the potential impact of a successful SQL injection attack by containing it within a restricted network segment.\n\n\n\n\n\n"
        }
      ]
    },
    "nvd.nist.gov": {
      "configurations": {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "children": [],
            "cpe_match": [
              {
                "cpe23Uri": "cpe:2.3:a:ardereg:sistemas_scada:*:*:*:*:*:*:*:*",
                "cpe_name": [],
                "versionEndIncluding": "2.203",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      },
      "cve": {
        "CVE_data_meta": {
          "ASSIGNER": "ics-cert@hq.dhs.gov",
          "ID": "CVE-2023-4485"
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "en",
              "value": "ARDEREG\u00a0?Sistema SCADA Central versions 2.203 and prior\nlogin page are vulnerable to an unauthenticated blind SQL injection attack. An attacker could manipulate the application\u0027s SQL query logic to extract sensitive information or perform unauthorized actions within the database. In this case, the vulnerability could allow an attacker to execute arbitrary SQL queries through the login page, potentially leading to unauthorized access, data leakage, or even disruption of critical industrial processes.\n\n"
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "en",
                  "value": "CWE-89"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-243-01",
              "refsource": "MISC",
              "tags": [
                "Third Party Advisory",
                "US Government Resource"
              ],
              "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-243-01"
            }
          ]
        }
      },
      "impact": {
        "baseMetricV3": {
          "cvssV3": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "exploitabilityScore": 3.9,
          "impactScore": 5.9
        }
      },
      "lastModifiedDate": "2023-09-11T18:00Z",
      "publishedDate": "2023-09-06T00:15Z"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…