CVE-2023-4125 json
Weak Password Requirements in answerdev/answer
published 2023-08-03 3 y ago modified 2026-06-17 4 mo ago also GHSA-j63x-f657-2m9g , GO-2023-2001 , EUVD-2023-2311
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
Weak Password Requirements in GitHub repository answerdev/answer prior to v1.1.0.
Patch / fix
- go github.com/answerdev/answer 1.1.0
- answerdev answerdev/answer v1.1.0
- answer answer 1.1.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.88% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/85bfd18f-8d3b-4154-8b7b-1f8fcf704e28 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/answerdev/answer | <1.1.0 |
1.1.0 |
Affected products
- answerdev answerdev/answer
- answer answer
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
github.com
/answerdev/answer/commit/7d23b17cdbbefcd2e7b5c3150f0b5ec908dc835f
web, patch
-
huntr.dev
/bounties/85bfd18f-8d3b-4154-8b7b-1f8fcf704e28
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-4125
advisory
-
github.com
/answerdev/answer
package
-
github.com
/advisories/GHSA-j63x-f657-2m9g
advisory
Sources
- CVE List CVE-2023-4125
- GitHub Advisory GHSA-j63x-f657-2m9g
- NVD CVE-2023-4125
- OSV GO-2023-2001
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.