ghsa-p8v3-m643-4xqx
Vulnerability from github
Published
2024-05-13 19:40
Modified
2024-05-14 20:04
Severity ?
Summary
Directus allows redacted data extraction on the API through "alias"
Details
Summary
A user with permission to view any collection using redacted hashed fields can get access the raw stored version using the alias functionality on the API.
Normally, these redacted fields will return ********** however if we change the request to ?alias[workaround]=redacted we can instead retrieve the plain text value for the field.
Steps to reproduce
- Set up a simple role with read-access to users.
- Create a new user with the role from the previous step
- Assign a password to the user
The easiest way to confirm this vulnerability is by first visiting /users/me. You should be presented with a redacted JSON-object.
Next, visit /users/me?alias[hash]=password. This time, the returned JSON object will included the raw password hash instead of the redacted value.
Workaround
This can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "directus"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "10.11.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-34708"
],
"database_specific": {
"cwe_ids": [
"CWE-200"
],
"github_reviewed": true,
"github_reviewed_at": "2024-05-13T19:40:08Z",
"nvd_published_at": "2024-05-14T15:39:31Z",
"severity": "MODERATE"
},
"details": "## Summary\nA user with permission to view any collection using redacted hashed fields can get access the raw stored version using the `alias` functionality on the API.\nNormally, these redacted fields will return `**********` however if we change the request to `?alias[workaround]=redacted` we can instead retrieve the plain text value for the field.\n\n## Steps to reproduce\n- Set up a simple role with read-access to users.\n- Create a new user with the role from the previous step\n- Assign a password to the user\n\nThe easiest way to confirm this vulnerability is by first visiting `/users/me`. You should be presented with a redacted JSON-object.\nNext, visit `/users/me?alias[hash]=password`. This time, the returned JSON object will included the raw password hash instead of the redacted value.\n\n## Workaround\nThis can be avoided by removing permission to view the sensitive fields entirely from users or roles that should not be able to see them.",
"id": "GHSA-p8v3-m643-4xqx",
"modified": "2024-05-14T20:04:22Z",
"published": "2024-05-13T19:40:08Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/directus/directus/security/advisories/GHSA-p8v3-m643-4xqx"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-34708"
},
{
"type": "WEB",
"url": "https://github.com/directus/directus/commit/e70a90c267bea695afce6545174c2b77517d617b"
},
{
"type": "PACKAGE",
"url": "https://github.com/directus/directus"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Directus allows redacted data extraction on the API through \"alias\""
}
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.