[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cve-CVE-2024-32474":3},{"id":4,"cve_id":5,"euvd_id":6,"summary":7,"published":8,"cvss_data":9,"is_remote":20,"cwes":21,"cpes":24,"technologies":26,"references":28,"score":35,"epss_score":36,"epss_percentile":37,"is_kev":38,"cisa_kev_date_added":39,"cisa_kev_due_date":39,"cisa_ssvc":40,"attack_mappings":50,"exploits":100},44370,"CVE-2024-32474","EUVD-2024-1123","Sentry vulnerable to leaking superuser cleartext password in logs\n\n### Impact\nWhen authenticating as a superuser to a self-hosted Sentry instance with a username and password, the password is leaked as cleartext in logs under the _event_: `auth-index.validate_superuser`. An attacker with access to the log data could use these leaked credentials to login to the Sentry system as superuser.\n\n### Patches\n- Self-hosted users on affected versions should upgrade to 24.4.1 or later.\n- Sentry SaaS users do not need to take any action. This vulnerability is not applicable to SaaS.\n\n### Workarounds\nUsers can configure the logging level to exclude logs of the `INFO` level and only generate logs for levels at `WARNING` or higher. For details on configuring self-hosted Sentry's logging level see our documentation at: https:\u002F\u002Fdevelop.sentry.dev\u002Fconfig\u002F#logging\n\n### References\n- Bug introduced in https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fpull\u002F66393\n- Security fix in https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fpull\u002F69148","2024-04-18T18:22:00Z",{"cvss_v3.1":10},{"scope":11,"version":12,"baseScore":13,"attackVector":14,"baseSeverity":15,"vectorString":16,"integrityImpact":15,"userInteraction":17,"attackComplexity":18,"availabilityImpact":19,"privilegesRequired":18,"confidentialityImpact":15},"UNCHANGED","3.1",7.3,"NETWORK","HIGH","CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:L\u002FUI:R\u002FS:U\u002FC:H\u002FI:H\u002FA:N","REQUIRED","LOW","NONE",true,[22,23],"CWE-117","CWE-312",[25],"cpe:2.3:a:sentry:sentry:*:*:*:*:*:*:*:*",[27],"Sentry Sentry",[29,30,31,32,33,34],"https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fcommit\u002Fd5b34568d9f1c41362ccb62141532a0a2169512f","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fpull\u002F66393","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fpull\u002F69148","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry\u002Fsecurity\u002Fadvisories\u002FGHSA-6cjm-4pxw-7xp9","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2024-32474","https:\u002F\u002Fgithub.com\u002Fgetsentry\u002Fsentry",0.56,0.00428,0.3673,false,null,{"timestamp":41,"automatable":42,"tech_impact":43,"exploitation":44,"cisa_decision":45,"cisa_remediation_timeline":49},"2024-04-23T14:22:52.411069Z","no","partial","none",{"vector":46,"decision":47,"priority":48},"CISAv1\u002FE:N\u002FA:N\u002FT:P\u002FM:H\u002F2026-10-25T17:38:48.978504\u002F","track_star","medium","60D",[51,57,66,74,81,88,94],{"name":52,"source":53,"tactics":54,"technique_id":56},"Exploit Public-Facing Application","attack_vector",[55],"initial-access","T1190",{"name":58,"source":59,"cwe_ids":60,"tactics":61,"capec_ids":63,"technique_id":65},"Data from Local System","capec",[23],[62],"collection",[64],"CAPEC-37","T1005",{"name":67,"source":59,"cwe_ids":68,"tactics":69,"capec_ids":71,"technique_id":73},"Indicator Removal",[22],[70],"stealth",[72],"CAPEC-268","T1070",{"name":75,"source":59,"cwe_ids":76,"tactics":77,"capec_ids":79,"technique_id":80},"Private Keys",[23],[78],"credential-access",[64],"T1552.004",{"name":82,"source":59,"cwe_ids":83,"tactics":84,"capec_ids":86,"technique_id":87},"Disable or Modify Windows Event Log",[22],[85],"defense-impairment",[72],"T1685.001",{"name":89,"source":59,"cwe_ids":90,"tactics":91,"capec_ids":92,"technique_id":93},"Disable or Modify Cloud Log",[22],[85],[72],"T1685.002",{"name":95,"source":59,"cwe_ids":96,"tactics":97,"capec_ids":98,"technique_id":99},"Prevent Command History Logging",[22],[85],[72],"T1690",[]]