CVE-2022-3798 json
IBAX go-ibax tablesInfo sql injection
published 2022-11-01 4 y ago modified 2026-06-17 4 mo ago also GHSA-mgqh-3qm7-gx82 , GO-2024-2777 , EUVD-2022-7385
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical has been found in IBAX go-ibax. Affected is an unknown function of the file /api/v2/open/tablesInfo. The manipulation leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-212634 is the identifier assigned to this vulnerability.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
| 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.1 | 8.8 | CVSS:3.1/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/IBAX-io/go-ibax | <1.4.2 |
1.4.2 |
Affected products
- IBAX go-ibax
Classification
References
-
github.com
/IBAX-io/go-ibax/commit/b0183d8e550836dc50282ee74ff421ee41b25a37
web, patch
-
github.com
/IBAX-io/go-ibax/issues/2060
web, issue-tracking, third-party-advisory, report
-
vuldb.com
/?id.212634
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-3798
advisory
-
github.com
/IBAX-io/go-ibax
package
-
github.com
/advisories/GHSA-mgqh-3qm7-gx82
advisory
Sources
- CVE List CVE-2022-3798
- GitHub Advisory GHSA-mgqh-3qm7-gx82
- NVD CVE-2022-3798
- OSV GO-2024-2777
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.