# CVE-2024-38363: Remote Code Execution (RCE) via Server Side Template Injection (SSTI) in Airbyte

> Authenticated attackers can execute arbitrary code via Server Side Template Injection in Airbyte's connection builder, potentially exposing sensitive credentials.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4j3c-fgvx-xgqq

## What is CVE-2024-38363?

CVE-2024-38363 is a high-severity code injection vulnerability in airbytehq airbyte, published on 9 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Airbyte is a data integration platform for ELT pipelines. Airbyte connection builder docker image is vulnerable to RCE via SSTI which allows an authenticated remote attacker to execute arbitrary code on the server as the web server user. The connection builder is used to create and test new connectors. Sensitive information, such as credentials, could be exposed if a user tested a new connector on a compromised instance. The connection builder does not have access to any data processes. This vulnerability is fixed in 0.62.2.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2024-38363?


## How do I fix CVE-2024-38363?

No fix has been published for CVE-2024-38363 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-38363 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-38363 and fix it if it is affected.

What it is: CVE-2024-38363 is a high-severity code injection vulnerability in airbytehq airbyte, published on 9 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38363 in the wild and no public exploit code.

Affected product: airbytehq airbyte. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-38363/ (Markdown: https://insights.sbomify.com/CVE-2024-38363/index.md)
```

## Sources

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

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