JVNDB-2005-000772
Vulnerability from jvndb - Published: 2008-05-21 00:00 - Updated:2008-05-21 00:00Summary
Inappropriate interpretation of mailto URL scheme by mail client software
Details
The mailto URL scheme is used to designate the Internet email address on a web page. Specifying an email address and body text using the mailto URL scheme gives a template for a mail message. Many mail clients have a function to set a field specified by the mailto URL scheme in a mail header.
RFC2368 defining the mailto URL scheme points out the followings in its Security Considerations section.
- A mail client should never send anything without complete disclosure to the user of the full message created based on descriptions of the mailto URL scheme
- It should explicitly display any headers along with the message destination.
- It is inappropriate to set a header related to mail delivery based on descriptions of the mailto URL scheme
However, some mail clients set the header related to mail delivery based on descriptions of the mailto URL scheme or do not explicitly display the full header.
We published this issue on JVN in coordination with developers, to publicize the issue to users and mail client developers.
References
Impacted products
{
"@rdf:about": "https://jvndb.jvn.jp/en/contents/2005/JVNDB-2005-000772.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": "The mailto URL scheme is used to designate the Internet email address on a web page. Specifying an email address and body text using the mailto URL scheme gives a template for a mail message. Many mail clients have a function to set a field specified by the mailto URL scheme in a mail header.\r\n\r\nRFC2368 defining the mailto URL scheme points out the followings in its Security Considerations section.\r\n\r\n- A mail client should never send anything without complete disclosure to the user of the full message created based on descriptions of the mailto URL scheme\r\n- It should explicitly display any headers along with the message destination.\r\n- It is inappropriate to set a header related to mail delivery based on descriptions of the mailto URL scheme \r\n\r\nHowever, some mail clients set the header related to mail delivery based on descriptions of the mailto URL scheme or do not explicitly display the full header.\r\n\r\nWe published this issue on JVN in coordination with developers, to publicize the issue to users and mail client developers.",
"link": "https://jvndb.jvn.jp/en/contents/2005/JVNDB-2005-000772.html",
"sec:cpe": [
{
"#text": "cpe:/a:allied_telesis_k.k.:at-mail_server",
"@product": "AT-Mail Server",
"@vendor": "Allied Telesis",
"@version": "2.2"
},
{
"#text": "cpe:/a:hidemaru:hidemaru_mail",
"@product": "Hidemaru Mail",
"@vendor": "Saitoh Kikaku",
"@version": "2.2"
},
{
"#text": "cpe:/a:justsystems:shuriken",
"@product": "Shuriken",
"@vendor": "JustSystems Corporation",
"@version": "2.2"
},
{
"#text": "cpe:/a:misc:edcom_edmax",
"@product": "EdMax",
"@vendor": "Edcom Inc. ",
"@version": "2.2"
},
{
"#text": "cpe:/a:misc:edcom_edmax_free",
"@product": "EdMax Free",
"@vendor": "Edcom Inc. ",
"@version": "2.2"
},
{
"#text": "cpe:/a:misc:orange_winbiff",
"@product": "Winbiff",
"@vendor": "Orangesoft Inc.",
"@version": "2.2"
},
{
"#text": "cpe:/a:rimarts_inc.:becky_internet_mail",
"@product": "Becky! Internet Mail",
"@vendor": "RIMARTS",
"@version": "2.2"
}
],
"sec:cvss": {
"@score": "4.3",
"@severity": "Medium",
"@type": "Base",
"@vector": "AV:N/AC:M/Au:N/C:N/I:P/A:N",
"@version": "2.0"
},
"sec:identifier": "JVNDB-2005-000772",
"sec:references": [
{
"#text": "http://jvn.jp/en/jp/JVNFCAD9BD8/index.html",
"@id": "JVN#FCAD9BD8",
"@source": "JVN"
},
{
"#text": "http://www.ietf.org/rfc/rfc2368.txt",
"@id": "RFC2368: The mailto URL scheme",
"@source": "IETF"
}
],
"title": "Inappropriate interpretation of mailto URL scheme by mail client software"
}
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…
Loading…