Home
» Security vulnerabilities
» CVE-2023-4124
Missing Authorization in GitHub repository answerdev/answer prior to v1.1.1.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-4124
Conclusion & alert: CVE-2023-4124 is rated Exploit Available (54.3/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2023-4124
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2023-4124
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-04-28
0.14%
0.17%
+0.03%
2
2026-03-14
0.15%
0.14%
-0.02%
3
2026-01-12
—
0.15%
—
Full EPSS history
(11 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-4124
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
6.5
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
3.6
[email protected]
8.1
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
5.2
[email protected]
Weakness enumeration for CVE-2023-4124
GitHub Security Advisory for CVE-2023-4124
GHSA-v9vc-7x69-c2x8 · Severity: high · Ecosystem: go
— Answer Missing Authorization vulnerability
Affected software / configurations for CVE-2023-4124
Vendor
Product
Version
Raw CPE
answer
answer
< 1.1.1
cpe:2.3:a:answer:answer:*:*:*:*:*:*:*:*
References for CVE-2023-4124
cvelogic
Threat Intelligence