CVE-2025-9824 (GCVE-0-2025-9824)
Vulnerability from cvelistv5
Published
2025-09-03 14:25
Modified
2025-09-03 14:46
Severity ?
VLAI Severity ?
EPSS score ?
CWE
Summary
ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.
PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.
Technical DetailsThe vulnerability was caused by different response times when:
* A valid username was provided (password hashing occurred)
* An invalid username was provided (no password hashing occurred)
The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.
WorkaroundsNo workarounds are available. Users should upgrade to the patched version.
References * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account
References
Impacted products
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2025-9824", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2025-09-03T14:45:46.949698Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2025-09-03T14:46:19.282Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" } ], "cna": { "affected": [ { "collectionURL": "https://packagist.org", "defaultStatus": "unaffected", "packageName": "mautic/core", "product": "Mautic", "repo": "https://github.com/mautic/mautic", "vendor": "Mautic", "versions": [ { "lessThan": "\u003c 4.4.17", "status": "affected", "version": "\u003e= 4.4.0", "versionType": "semver" }, { "lessThan": "\u003c 5.2.8", "status": "affected", "version": "\u003e= 5.0.0-alpha", "versionType": "semver" }, { "lessThan": "\u003c 6.0.5", "status": "affected", "version": "\u003e= 6.0.0-alpha", "versionType": "semver" } ] } ], "credits": [ { "lang": "en", "type": "reporter", "value": "Vautia" }, { "lang": "en", "type": "remediation reviewer", "value": "kuzmany" }, { "lang": "en", "type": "remediation developer", "value": "nick-vanpraet" } ], "datePublic": "2025-09-03T08:56:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "\u003ch3\u003eImpact\u003c/h3\u003e\u003cp\u003eThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.\u003c/p\u003e\u003ch3\u003ePatches\u003c/h3\u003e\u003cp\u003eThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\u003c/p\u003e\u003ch3\u003eTechnical Details\u003c/h3\u003e\u003cp\u003eThe vulnerability was caused by different response times when:\u003c/p\u003e\u003cul\u003e\u003cli\u003eA valid username was provided (password hashing occurred)\u003c/li\u003e\u003cli\u003eAn invalid username was provided (no password hashing occurred)\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eThe fix introduces a \u003ccode\u003eTimingSafeFormLoginAuthenticator\u003c/code\u003e\u0026nbsp;that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\u003c/p\u003e\u003ch3\u003eWorkarounds\u003c/h3\u003e\u003cp\u003eNo workarounds are available. Users should upgrade to the patched version.\u003c/p\u003e\u003ch3\u003eReferences\u003c/h3\u003e\u003cul\u003e\u003cli\u003e\u003ca target=\"_blank\" rel=\"nofollow\" href=\"https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\"\u003ehttps://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\u003c/a\u003e\u003c/li\u003e\u003c/ul\u003e" } ], "value": "ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.\n\nPatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\n\nTechnical DetailsThe vulnerability was caused by different response times when:\n\n * A valid username was provided (password hashing occurred)\n * An invalid username was provided (no password hashing occurred)\n\n\nThe fix introduces a TimingSafeFormLoginAuthenticator\u00a0that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\n\nWorkaroundsNo workarounds are available. Users should upgrade to the patched version.\n\nReferences * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account" } ], "impacts": [ { "capecId": "CAPEC-172", "descriptions": [ { "lang": "en", "value": "CAPEC-172" } ] } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 5.9, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1" }, "format": "CVSS", "scenarios": [ { "lang": "en", "value": "GENERAL" } ] } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-204", "description": "CWE-204", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2025-09-03T14:25:06.796Z", "orgId": "4e531c38-7a33-45d3-98dd-d909c0d8852e", "shortName": "Mautic" }, "references": [ { "url": "https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg" } ], "source": { "advisory": "GHSA-3ggv-qwcp-j6xg", "discovery": "EXTERNAL" }, "title": "User Enumeration via Response Timing", "x_generator": { "engine": "Vulnogram 0.2.0" } } }, "cveMetadata": { "assignerOrgId": "4e531c38-7a33-45d3-98dd-d909c0d8852e", "assignerShortName": "Mautic", "cveId": "CVE-2025-9824", "datePublished": "2025-09-03T14:25:06.796Z", "dateReserved": "2025-09-02T08:28:30.562Z", "dateUpdated": "2025-09-03T14:46:19.282Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2025-9824\",\"sourceIdentifier\":\"security@mautic.org\",\"published\":\"2025-09-03T15:15:49.413\",\"lastModified\":\"2025-09-04T15:35:29.497\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.\\n\\nPatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\\n\\nTechnical DetailsThe vulnerability was caused by different response times when:\\n\\n * A valid username was provided (password hashing occurred)\\n * An invalid username was provided (no password hashing occurred)\\n\\n\\nThe fix introduces a TimingSafeFormLoginAuthenticator\u00a0that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\\n\\nWorkaroundsNo workarounds are available. Users should upgrade to the patched version.\\n\\nReferences * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security@mautic.org\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.9,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.2,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"security@mautic.org\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-204\"}]}],\"references\":[{\"url\":\"https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg\",\"source\":\"security@mautic.org\"}]}}", "vulnrichment": { "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-9824\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-09-03T14:45:46.949698Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-09-03T14:46:05.522Z\"}}], \"cna\": {\"title\": \"User Enumeration via Response Timing\", \"source\": {\"advisory\": \"GHSA-3ggv-qwcp-j6xg\", \"discovery\": \"EXTERNAL\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"reporter\", \"value\": \"Vautia\"}, {\"lang\": \"en\", \"type\": \"remediation reviewer\", \"value\": \"kuzmany\"}, {\"lang\": \"en\", \"type\": \"remediation developer\", \"value\": \"nick-vanpraet\"}], \"impacts\": [{\"capecId\": \"CAPEC-172\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-172\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.9, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"NONE\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"repo\": \"https://github.com/mautic/mautic\", \"vendor\": \"Mautic\", \"product\": \"Mautic\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 4.4.0\", \"lessThan\": \"\u003c 4.4.17\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"\u003e= 5.0.0-alpha\", \"lessThan\": \"\u003c 5.2.8\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"\u003e= 6.0.0-alpha\", \"lessThan\": \"\u003c 6.0.5\", \"versionType\": \"semver\"}], \"packageName\": \"mautic/core\", \"collectionURL\": \"https://packagist.org\", \"defaultStatus\": \"unaffected\"}], \"datePublic\": \"2025-09-03T08:56:00.000Z\", \"references\": [{\"url\": \"https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg\"}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.\\n\\nPatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\\n\\nTechnical DetailsThe vulnerability was caused by different response times when:\\n\\n * A valid username was provided (password hashing occurred)\\n * An invalid username was provided (no password hashing occurred)\\n\\n\\nThe fix introduces a TimingSafeFormLoginAuthenticator\\u00a0that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\\n\\nWorkaroundsNo workarounds are available. Users should upgrade to the patched version.\\n\\nReferences * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003ch3\u003eImpact\u003c/h3\u003e\u003cp\u003eThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks.\u003c/p\u003e\u003ch3\u003ePatches\u003c/h3\u003e\u003cp\u003eThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\u003c/p\u003e\u003ch3\u003eTechnical Details\u003c/h3\u003e\u003cp\u003eThe vulnerability was caused by different response times when:\u003c/p\u003e\u003cul\u003e\u003cli\u003eA valid username was provided (password hashing occurred)\u003c/li\u003e\u003cli\u003eAn invalid username was provided (no password hashing occurred)\u003c/li\u003e\u003c/ul\u003e\u003cp\u003eThe fix introduces a \u003ccode\u003eTimingSafeFormLoginAuthenticator\u003c/code\u003e\u0026nbsp;that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\u003c/p\u003e\u003ch3\u003eWorkarounds\u003c/h3\u003e\u003cp\u003eNo workarounds are available. Users should upgrade to the patched version.\u003c/p\u003e\u003ch3\u003eReferences\u003c/h3\u003e\u003cul\u003e\u003cli\u003e\u003ca target=\\\"_blank\\\" rel=\\\"nofollow\\\" href=\\\"https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\\\"\u003ehttps://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account\u003c/a\u003e\u003c/li\u003e\u003c/ul\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-204\", \"description\": \"CWE-204\"}]}], \"providerMetadata\": {\"orgId\": \"4e531c38-7a33-45d3-98dd-d909c0d8852e\", \"shortName\": \"Mautic\", \"dateUpdated\": \"2025-09-03T14:25:06.796Z\"}}}", "cveMetadata": "{\"cveId\": \"CVE-2025-9824\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-09-03T14:46:19.282Z\", \"dateReserved\": \"2025-09-02T08:28:30.562Z\", \"assignerOrgId\": \"4e531c38-7a33-45d3-98dd-d909c0d8852e\", \"datePublished\": \"2025-09-03T14:25:06.796Z\", \"assignerShortName\": \"Mautic\"}", "dataType": "CVE_RECORD", "dataVersion": "5.1" } } }
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.
Loading…