FKIE_CVE-2019-12923
Vulnerability from fkie_nvd - Published: 2019-07-08 21:15 - Updated: 2024-11-21 04:23
Severity ?
Summary
In MailEnable Enterprise Premium 10.23, the potential cross-site request forgery (CSRF) protection mechanism was not implemented correctly and it was possible to bypass it by removing the anti-CSRF token parameter from the request. This could allow an attacker to manipulate a user into unwittingly performing actions within the application (such as sending email, adding contacts, or changing settings) on behalf of the attacker.
References
| URL | Tags | ||
|---|---|---|---|
| cve@mitre.org | http://www.mailenable.com/Premium-ReleaseNotes.txt | Release Notes, Vendor Advisory | |
| cve@mitre.org | https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/ | Release Notes, Third Party Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | http://www.mailenable.com/Premium-ReleaseNotes.txt | Release Notes, Vendor Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/ | Release Notes, Third Party Advisory |
Impacted products
| Vendor | Product | Version | |
|---|---|---|---|
| mailenable | mailenable | * | |
| mailenable | mailenable | * | |
| mailenable | mailenable | * | |
| mailenable | mailenable | * | |
| mailenable | mailenable | * |
{
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*",
"matchCriteriaId": "F7B4998A-BD40-4D0D-AC78-0457F40067C0",
"versionEndExcluding": "6.90",
"versionStartIncluding": "6.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*",
"matchCriteriaId": "9B9FFD5C-6982-4B54-BED3-DBAF30490439",
"versionEndExcluding": "7.62",
"versionStartIncluding": "7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*",
"matchCriteriaId": "1FAD50A0-D3E4-40B7-80DB-AD741B1BE1E6",
"versionEndExcluding": "8.64",
"versionStartIncluding": "8.00",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*",
"matchCriteriaId": "5DCC3F1A-6A49-4A2B-B973-1A44EFEF675B",
"versionEndExcluding": "9.83",
"versionStartIncluding": "9.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*",
"matchCriteriaId": "55F2A0A6-2BA0-4176-B9A2-9E2A86635BC2",
"versionEndExcluding": "10.24",
"versionStartIncluding": "10.00",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In MailEnable Enterprise Premium 10.23, the potential cross-site request forgery (CSRF) protection mechanism was not implemented correctly and it was possible to bypass it by removing the anti-CSRF token parameter from the request. This could allow an attacker to manipulate a user into unwittingly performing actions within the application (such as sending email, adding contacts, or changing settings) on behalf of the attacker."
},
{
"lang": "es",
"value": "En MailEnable Enterprise Premium versi\u00f3n 10.23, el mecanismo de protecci\u00f3n contra un potencial problema de tipo cross-site request forgery (CSRF) no se implement\u00f3 correctamente y fue posible omitirlo eliminando el par\u00e1metro token anti-CSRF de la petici\u00f3n. Esto podr\u00eda permitir a un atacante manipular a un usuario para que, involuntariamente, realice acciones dentro de la aplicaci\u00f3n (tales como enviar correos electr\u00f3nicos, agregar contactos o cambiar la configuraci\u00f3n) en nombre del atacante."
}
],
"id": "CVE-2019-12923",
"lastModified": "2024-11-21T04:23:49.797",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "MEDIUM",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"confidentialityImpact": "NONE",
"integrityImpact": "PARTIAL",
"vectorString": "AV:N/AC:M/Au:N/C:N/I:P/A:N",
"version": "2.0"
},
"exploitabilityScore": 8.6,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": true
}
],
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 2.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2019-07-08T21:15:09.957",
"references": [
{
"source": "cve@mitre.org",
"tags": [
"Release Notes",
"Vendor Advisory"
],
"url": "http://www.mailenable.com/Premium-ReleaseNotes.txt"
},
{
"source": "cve@mitre.org",
"tags": [
"Release Notes",
"Third Party Advisory"
],
"url": "https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes",
"Vendor Advisory"
],
"url": "http://www.mailenable.com/Premium-ReleaseNotes.txt"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Release Notes",
"Third Party Advisory"
],
"url": "https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/"
}
],
"sourceIdentifier": "cve@mitre.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-352"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
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…