Improper Access Control in GitHub repository answerdev/answer prior to 1.0.4.
Loading...
Loading...
This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 8.5%, top 8% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Improper Access Control in GitHub repository answerdev/answer prior to 1.0.4.
February 8, 2023
November 21, 2024
Fix landed in answerdev/answer commit c1fa2b13f6b5 — awaiting tagged release
https://github.com/answerdev/answer/commit/c1fa2b13f6b547b96da60b23350bbe2b29de542d| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/answerdev/answer | — | 1.0.4 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-0744
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.