# CVE-2022-3798: IBAX go-ibax tablesInfo sql injection

> Remote attackers can exploit SQL injection in the tablesInfo API to read or modify database contents in IBAX go-ibax.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Nov 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-mgqh-3qm7-gx82, GO-2024-2777

## What is CVE-2022-3798?

CVE-2022-3798 is a medium-severity SQL injection vulnerability in go-ibax, published on 1 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-707 (Improper Neutralization)

## Which versions are affected by CVE-2022-3798?

3 open source packages ship an affected version, including github.com/IBAX-io/go-ibax. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/IBAX-io/go-ibax` | Go | All versions | 1.4.2 |
| `github.com/IBAX-io/go-ibax` | Go | All versions | 1.4.2 |
| `github.com/IBAX-io/go-ibax` | Go | All versions | 1.4.2 |

Products: Ibax Go-Ibax.

## How do I fix CVE-2022-3798?

Upgrade github.com/IBAX-io/go-ibax to 1.4.2 or later.

## Is CVE-2022-3798 being exploited?

There is no known exploitation of CVE-2022-3798 in the wild and no public exploit code.

## Other vulnerabilities in go-ibax

- [CVE-2022-3799](https://insights.sbomify.com/CVE-2022-3799/): IBAX go-ibax tablesInfo sql injection (medium 6.3)
- [CVE-2022-3800](https://insights.sbomify.com/CVE-2022-3800/): IBAX go-ibax rowsInfo sql injection (medium 6.3)
- [CVE-2022-3801](https://insights.sbomify.com/CVE-2022-3801/): IBAX go-ibax rowsInfo sql injection (medium 6.3)
- [CVE-2022-3802](https://insights.sbomify.com/CVE-2022-3802/): IBAX go-ibax rowsInfo sql injection (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3798 and fix it if it is affected.

What it is: CVE-2022-3798 is a medium-severity SQL injection vulnerability in go-ibax, published on 1 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3798 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/IBAX-io/go-ibax (Go): affected all versions; fixed in 1.4.2
- github.com/IBAX-io/go-ibax (Go): affected all versions; fixed in 1.4.2
- github.com/IBAX-io/go-ibax (Go): affected all versions; fixed in 1.4.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3798/ (Markdown: https://insights.sbomify.com/CVE-2022-3798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3798
- OSV: https://osv.dev/vulnerability/CVE-2022-3798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3798/
Summaries are generated and may contain mistakes; the official description above is the record.