fkie_cve-2023-7017
Vulnerability from fkie_nvd
Published
2024-03-15 17:15
Modified
2025-11-04 19:16
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
Sciener locks' firmware update mechanism do not authenticate or validate firmware updates if passed to the lock through the Bluetooth Low Energy service. A challenge request can be sent to the lock with a command to prepare for an update, rather than an unlock request, allowing an attacker to compromise the device.
References
cret@cert.orghttps://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/
af854a3a-2127-422b-91ae-364da2661108https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/
af854a3a-2127-422b-91ae-364da2661108https://www.kb.cert.org/vuls/id/949046
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Sciener locks\u0027 firmware update mechanism do not authenticate or validate firmware updates if passed to the lock through the Bluetooth Low Energy service. A challenge request can be sent to the lock with a command to prepare for an update, rather than an unlock request, allowing an attacker to compromise the device."
    },
    {
      "lang": "es",
      "value": "El mecanismo de actualizaci\u00f3n de firmware de las cerraduras Sciener no autentica ni valida las actualizaciones de firmware si se pasan a la cerradura a trav\u00e9s del servicio Bluetooth Low Energy. Se puede enviar una solicitud de desaf\u00edo a la cerradura con un comando para prepararse para una actualizaci\u00f3n, en lugar de una solicitud de desbloqueo, lo que permite a un atacante comprometer el dispositivo."
    }
  ],
  "id": "CVE-2023-7017",
  "lastModified": "2025-11-04T19:16:26.230",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "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,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2024-03-15T17:15:07.857",
  "references": [
    {
      "source": "cret@cert.org",
      "url": "https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://alephsecurity.com/2024/03/07/kontrol-lux-lock-2/"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://www.kb.cert.org/vuls/id/949046"
    }
  ],
  "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.