Vulnerability from bitnami_vulndb
Published
2024-05-14 14:38
Modified
2025-05-20 10:02
Summary
Privilege escalation from having CREATE access on a keyspace in Scylladb
Details
Scylladb is a NoSQL data store using the seastar framework, compatible with Apache Cassandra. Authenticated users who are authorized to create tables in a keyspace can escalate their privileges to access a table in the same keyspace, even if they don't have permissions for that table. This issue has not yet been patched. A workaround to address this issue is to disable CREATE privileges on a keyspace, and create new tables on behalf of other users.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "scylladb",
"purl": "pkg:bitnami/scylladb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.2.9"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2023-33972"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:scylladb:scylladb:*:*:*:*:*:*:*:*"
],
"severity": "High"
},
"details": "Scylladb is a NoSQL data store using the seastar framework, compatible with Apache Cassandra. Authenticated users who are authorized to create tables in a keyspace can escalate their privileges to access a table in the same keyspace, even if they don\u0027t have permissions for that table. This issue has not yet been patched. A workaround to address this issue is to disable CREATE privileges on a keyspace, and create new tables on behalf of other users.",
"id": "BIT-scylladb-2023-33972",
"modified": "2025-05-20T10:02:07.006Z",
"published": "2024-05-14T14:38:04.732Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/scylladb/scylladb/security/advisories/GHSA-ww5v-p45p-3vhq"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-33972"
}
],
"schema_version": "1.5.0",
"summary": "Privilege escalation from having CREATE access on a keyspace in Scylladb"
}
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…