gsd-2023-7003
Vulnerability from gsd
Modified
2023-12-21 06:01
Details
The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware.
Aliases


To clipboard 

{
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-7003"
      ],
      "details": "The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware.",
      "id": "GSD-2023-7003",
      "modified": "2023-12-21T06:01:24.597622Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "cert@cert.org",
        "ID": "CVE-2023-7003",
        "STATE": "PUBLIC"
      },
      "affects": {
        "vendor": {
          "vendor_data": [
            {
              "product": {
                "product_data": [
                  {
                    "product_name": "Kontrol Lux",
                    "version": {
                      "version_data": [
                        {
                          "version_affected": "\u003c=",
                          "version_name": "6.5.x",
                          "version_value": "6.5.07"
                        }
                      ]
                    }
                  }
                ]
              },
              "vendor_name": "Sciener"
            }
          ]
        }
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware."
          }
        ]
      },
      "generator": {
        "engine": "VINCE 2.1.11",
        "env": "prod",
        "origin": "https://cveawg.mitre.org/api/cve/CVE-2023-7003"
      },
      "problemtype": {
        "problemtype_data": [
          {
            "description": [
              {
                "lang": "eng",
                "value": "CWE-321: Use of Hard-coded Cryptographic Key"
              }
            ]
          }
        ]
      },
      "references": {
        "reference_data": [
          {
            "name": "https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/",
            "refsource": "MISC",
            "url": "https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/"
          }
        ]
      },
      "source": {
        "discovery": "UNKNOWN"
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "descriptions": [
          {
            "lang": "en",
            "value": "The AES key utilized in the pairing process between a lock using Sciener firmware and a wireless keypad is not unique, and can be reused to compromise other locks using the Sciener firmware."
          },
          {
            "lang": "es",
            "value": "La clave AES utilizada en el proceso de emparejamiento entre una cerradura que usa el firmware Sciener y un teclado inal\u00e1mbrico no es \u00fanica y puede reutilizarse para comprometer otras cerraduras que usan el firmware Sciener."
          }
        ],
        "id": "CVE-2023-7003",
        "lastModified": "2024-03-17T22:38:29.433",
        "metrics": {},
        "published": "2024-03-15T17:15:07.630",
        "references": [
          {
            "source": "cret@cert.org",
            "url": "https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/"
          }
        ],
        "sourceIdentifier": "cret@cert.org",
        "vulnStatus": "Awaiting Analysis"
      }
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.