JVNDB-2005-000756

Vulnerability from jvndb - Published: 2008-05-21 00:00 - Updated:2008-05-21 00:00
Severity ?
() - -
Summary
Tsuru-Kame Mail vulnerable in S/MIME signature verification
Details
Tsuru-Kame Mail contains the following vulnerabilities in the S/MIME signature verification: - S/MIME signature verification does not verify the certification path. - S/MIME signature verification does not verify the certification expiration date. The name of the software "Tsuru-Kame Mail" was changed to "Hidemaru Mail" on August 10, 2005.
References
Impacted products
Show details on JVN DB website
To clipboard 

{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2005/JVNDB-2005-000756.html",
  "dc:date": "2008-05-21T00:00+09:00",
  "dcterms:issued": "2008-05-21T00:00+09:00",
  "dcterms:modified": "2008-05-21T00:00+09:00",
  "description": "Tsuru-Kame Mail contains the following vulnerabilities in the S/MIME signature verification:\r\n- S/MIME signature verification does not verify the certification path.\r\n- S/MIME signature verification does not verify the certification expiration date.\r\n\r\nThe name of the software \"Tsuru-Kame Mail\" was changed to \"Hidemaru Mail\" on August 10, 2005.",
  "link": "https://jvndb.jvn.jp/en/contents/2005/JVNDB-2005-000756.html",
  "sec:cpe": {
    "#text": "cpe:/a:hidemaru:hidemaru_mail",
    "@product": "Hidemaru Mail",
    "@vendor": "Saitoh Kikaku",
    "@version": "2.2"
  },
  "sec:cvss": {
    "@score": "5.0",
    "@severity": "Medium",
    "@type": "Base",
    "@vector": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
    "@version": "2.0"
  },
  "sec:identifier": "JVNDB-2005-000756",
  "sec:references": {
    "#text": "http://jvn.jp/en/jp/JVNE59B594B/index.html",
    "@id": "JVN#E59B594B",
    "@source": "JVN"
  },
  "title": "Tsuru-Kame Mail vulnerable in S/MIME signature verification"
}


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



Detection rules are retrieved from Rulezet.