jvndb-2024-000086
Vulnerability from jvndb
Published
2024-08-22 13:51
Modified
2024-08-29 12:23
Severity ?
Summary
Multiple Safie products vulnerable to improper server certificate verification
Details
Multiple Safie products are vulnerable to improper server certificate verification (CWE-295). The product can be operated via port 11029/TCP and Bluetooth, and its communications are AES encrypted. The product user can obtain the encryption key from the cloud server based on the device-specific information. The user who has obtained the device-specific information can directly operate the device (even if it is not owned by the user). Taizoh Tsukamoto of Mitsui Bussan Secure Directions, Inc. reported these vulnerabilities to IPA. JPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.
Impacted products
Show details on JVN DB website


{
   "@rdf:about": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-000086.html",
   "dc:date": "2024-08-29T12:23+09:00",
   "dcterms:issued": "2024-08-22T13:51+09:00",
   "dcterms:modified": "2024-08-29T12:23+09:00",
   description: "Multiple Safie products are vulnerable to improper server certificate verification (CWE-295).\r\nThe product can be operated via port 11029/TCP and Bluetooth, and its communications are AES encrypted. The product user can obtain the encryption key from the cloud server based on the device-specific information. The user who has obtained the device-specific information can directly operate the device (even if it is not owned by the user).\r\n\r\nTaizoh Tsukamoto of Mitsui Bussan Secure Directions, Inc. reported these vulnerabilities to IPA.\r\nJPCERT/CC coordinated with the developer under Information Security Early Warning Partnership.",
   link: "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-000086.html",
   "sec:cpe": [
      {
         "#text": "cpe:/a:misc:safie_qbic_cloud_cc-2l",
         "@product": "QBiC CLOUD CC-2L",
         "@vendor": "Safie Inc.",
         "@version": "2.2",
      },
      {
         "#text": "cpe:/a:misc:safie_safie_one",
         "@product": "Safie One",
         "@vendor": "Safie Inc.",
         "@version": "2.2",
      },
   ],
   "sec:cvss": {
      "@score": "4.2",
      "@severity": "Medium",
      "@type": "Base",
      "@vector": "CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
      "@version": "3.0",
   },
   "sec:identifier": "JVNDB-2024-000086",
   "sec:references": [
      {
         "#text": "https://jvn.jp/en/jp/JVN83440451/index.html",
         "@id": "JVN#83440451",
         "@source": "JVN",
      },
      {
         "#text": "https://www.cve.org/CVERecord?id=CVE-2024-39771",
         "@id": "CVE-2024-39771",
         "@source": "CVE",
      },
      {
         "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
         "@id": "CWE-Other",
         "@title": "No Mapping(CWE-Other)",
      },
   ],
   title: "Multiple Safie products vulnerable to improper server certificate verification",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.
  • 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.