CVE-2024-35196 (GCVE-0-2024-35196)
Vulnerability from cvelistv5 – Published: 2024-05-31 17:25 – Updated: 2024-08-02 03:07
VLAI?
Title
Slack integration leaks sensitive information in logs in Sentry
Summary
Sentry is a developer-first error tracking and performance monitoring platform. Sentry's Slack integration incorrectly records the incoming request body in logs. This request data can contain sensitive information, including the deprecated Slack verification token. With this verification token, it is possible under specific configurations, an attacker can forge requests and act as the Slack integration. The request body is leaked in log entries matching `event == "slack.*" && name == "sentry.integrations.slack" && request_data == *`. The deprecated slack verification token, will be found in the `request_data.token` key. **SaaS users** do not need to take any action. **Self-hosted users** should upgrade to version 24.5.0 or higher, rotate their Slack verification token, and use the Slack Signing Secret instead of the verification token. For users only using the `slack.signing-secret` in their self-hosted configuration, the legacy verification token is not used to verify the webhook payload. It is ignored. Users unable to upgrade should either set the `slack.signing-secret` instead of `slack.verification-token`. The signing secret is Slack's recommended way of authenticating webhooks. By having `slack.singing-secret` set, Sentry self-hosted will no longer use the verification token for authentication of the webhooks, regardless of whether `slack.verification-token` is set or not. Alternatively if the self-hosted instance is unable to be upgraded or re-configured to use the `slack.signing-secret`, the logging configuration can be adjusted to not generate logs from the integration. The default logging configuration can be found in `src/sentry/conf/server.py`. **Services should be restarted once the configuration change is saved.**
Severity ?
CWE
- CWE-532 - Insertion of Sensitive Information into Log File
Assigner
References
| URL | Tags | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-35196",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-06-06T18:04:07.244703Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-06-06T18:04:18.333Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2024-08-02T03:07:46.866Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"name": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j",
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j"
},
{
"name": "https://github.com/getsentry/sentry/pull/70508",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://github.com/getsentry/sentry/pull/70508"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating"
},
{
"name": "https://develop.sentry.dev/integrations/slack",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://develop.sentry.dev/integrations/slack"
},
{
"name": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307",
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "sentry",
"vendor": "getsentry",
"versions": [
{
"status": "affected",
"version": "\u003e= 24.3.0, \u003c 24.5.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Sentry is a developer-first error tracking and performance monitoring platform. Sentry\u0027s Slack integration incorrectly records the incoming request body in logs. This request data can contain sensitive information, including the deprecated Slack verification token. With this verification token, it is possible under specific configurations, an attacker can forge requests and act as the Slack integration. The request body is leaked in log entries matching `event == \"slack.*\" \u0026\u0026 name == \"sentry.integrations.slack\" \u0026\u0026 request_data == *`. The deprecated slack verification token, will be found in the `request_data.token` key. **SaaS users** do not need to take any action. **Self-hosted users** should upgrade to version 24.5.0 or higher, rotate their Slack verification token, and use the Slack Signing Secret instead of the verification token. For users only using the `slack.signing-secret` in their self-hosted configuration, the legacy verification token is not used to verify the webhook payload. It is ignored. Users unable to upgrade should either set the `slack.signing-secret` instead of `slack.verification-token`. The signing secret is Slack\u0027s recommended way of authenticating webhooks. By having `slack.singing-secret` set, Sentry self-hosted will no longer use the verification token for authentication of the webhooks, regardless of whether `slack.verification-token` is set or not. Alternatively if the self-hosted instance is unable to be upgraded or re-configured to use the `slack.signing-secret`, the logging configuration can be adjusted to not generate logs from the integration. The default logging configuration can be found in `src/sentry/conf/server.py`. **Services should be restarted once the configuration change is saved.**\n"
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 2,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "HIGH",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-532",
"description": "CWE-532: Insertion of Sensitive Information into Log File",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2024-05-31T17:26:07.151Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j"
},
{
"name": "https://github.com/getsentry/sentry/pull/70508",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/getsentry/sentry/pull/70508"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates",
"tags": [
"x_refsource_MISC"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation",
"tags": [
"x_refsource_MISC"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#deprecation"
},
{
"name": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating",
"tags": [
"x_refsource_MISC"
],
"url": "https://api.slack.com/authentication/verifying-requests-from-slack#regenerating"
},
{
"name": "https://develop.sentry.dev/integrations/slack",
"tags": [
"x_refsource_MISC"
],
"url": "https://develop.sentry.dev/integrations/slack"
},
{
"name": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307"
}
],
"source": {
"advisory": "GHSA-c2g2-gx4j-rj3j",
"discovery": "UNKNOWN"
},
"title": "Slack integration leaks sensitive information in logs in Sentry"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2024-35196",
"datePublished": "2024-05-31T17:25:55.716Z",
"dateReserved": "2024-05-10T14:24:24.342Z",
"dateUpdated": "2024-08-02T03:07:46.866Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j\", \"name\": \"https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j\", \"tags\": [\"x_refsource_CONFIRM\", \"x_transferred\"]}, {\"url\": \"https://github.com/getsentry/sentry/pull/70508\", \"name\": \"https://github.com/getsentry/sentry/pull/70508\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#deprecation\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#deprecation\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#regenerating\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#regenerating\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}, {\"url\": \"https://develop.sentry.dev/integrations/slack\", \"name\": \"https://develop.sentry.dev/integrations/slack\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}, {\"url\": \"https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307\", \"name\": \"https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307\", \"tags\": [\"x_refsource_MISC\", \"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T03:07:46.866Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-35196\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-06-06T18:04:07.244703Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-06-06T18:04:14.637Z\"}}], \"cna\": {\"title\": \"Slack integration leaks sensitive information in logs in Sentry\", \"source\": {\"advisory\": \"GHSA-c2g2-gx4j-rj3j\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 2, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"LOW\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"REQUIRED\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"HIGH\", \"confidentialityImpact\": \"LOW\"}}], \"affected\": [{\"vendor\": \"getsentry\", \"product\": \"sentry\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 24.3.0, \u003c 24.5.0\"}]}], \"references\": [{\"url\": \"https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j\", \"name\": \"https://github.com/getsentry/sentry/security/advisories/GHSA-c2g2-gx4j-rj3j\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/getsentry/sentry/pull/70508\", \"name\": \"https://github.com/getsentry/sentry/pull/70508\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#app-management-updates\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#deprecation\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#deprecation\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://api.slack.com/authentication/verifying-requests-from-slack#regenerating\", \"name\": \"https://api.slack.com/authentication/verifying-requests-from-slack#regenerating\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://develop.sentry.dev/integrations/slack\", \"name\": \"https://develop.sentry.dev/integrations/slack\", \"tags\": [\"x_refsource_MISC\"]}, {\"url\": \"https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307\", \"name\": \"https://github.com/getsentry/sentry/blob/17d2b87e39ccd57e11da4deed62971ff306253d1/src/sentry/conf/server.py#L1307\", \"tags\": [\"x_refsource_MISC\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"Sentry is a developer-first error tracking and performance monitoring platform. Sentry\u0027s Slack integration incorrectly records the incoming request body in logs. This request data can contain sensitive information, including the deprecated Slack verification token. With this verification token, it is possible under specific configurations, an attacker can forge requests and act as the Slack integration. The request body is leaked in log entries matching `event == \\\"slack.*\\\" \u0026\u0026 name == \\\"sentry.integrations.slack\\\" \u0026\u0026 request_data == *`. The deprecated slack verification token, will be found in the `request_data.token` key. **SaaS users** do not need to take any action. **Self-hosted users** should upgrade to version 24.5.0 or higher, rotate their Slack verification token, and use the Slack Signing Secret instead of the verification token. For users only using the `slack.signing-secret` in their self-hosted configuration, the legacy verification token is not used to verify the webhook payload. It is ignored. Users unable to upgrade should either set the `slack.signing-secret` instead of `slack.verification-token`. The signing secret is Slack\u0027s recommended way of authenticating webhooks. By having `slack.singing-secret` set, Sentry self-hosted will no longer use the verification token for authentication of the webhooks, regardless of whether `slack.verification-token` is set or not. Alternatively if the self-hosted instance is unable to be upgraded or re-configured to use the `slack.signing-secret`, the logging configuration can be adjusted to not generate logs from the integration. The default logging configuration can be found in `src/sentry/conf/server.py`. **Services should be restarted once the configuration change is saved.**\\n\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-532\", \"description\": \"CWE-532: Insertion of Sensitive Information into Log File\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2024-05-31T17:26:07.151Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-35196\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-08-02T03:07:46.866Z\", \"dateReserved\": \"2024-05-10T14:24:24.342Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2024-05-31T17:25:55.716Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
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…