# CVE-2007-3388: Code injection in n/a > Remote attackers can execute arbitrary code via format string vulnerabilities in Qt 3 error message handling, requiring user interaction to trigger. - **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 3 Aug 2007 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-f86g-8g2c-pghw, RHSA-2007:0721 ## What is CVE-2007-3388? CVE-2007-3388 is a medium-severity code injection vulnerability in n/a, published on 3 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Multiple format string vulnerabilities in (1) qtextedit.cpp, (2) qdatatable.cpp, (3) qsqldatabase.cpp, (4) qsqlindex.cpp, (5) qsqlrecord.cpp, (6) qglobal.cpp, and (7) qsvgdevice.cpp in QTextEdit in Trolltech Qt 3 before 3.3.8 20070727 allow remote attackers to execute arbitrary code via format string specifiers in text used to compose an error message. ## Which versions are affected by CVE-2007-3388? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `qt` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-MySQL` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-ODBC` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-config` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-designer` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt-devel` | Red Hat:enterprise_linux:3::as | All versions | 1:3.1.2-16.RHEL3 | | `qt` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-MySQL` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-ODBC` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-config` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-designer` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 1:3.1.2-16.RHEL3 | | `qt` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-MySQL` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-ODBC` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-config` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-designer` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt-devel` | Red Hat:enterprise_linux:3::es | All versions | 1:3.1.2-16.RHEL3 | | `qt` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-MySQL` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-ODBC` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-config` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-designer` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt-devel` | Red Hat:enterprise_linux:3::ws | All versions | 1:3.1.2-16.RHEL3 | | `qt` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-MySQL` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-ODBC` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-PostgreSQL` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-config` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-designer` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt-devel` | Red Hat:enterprise_linux:4::as | All versions | 1:3.3.3-11.RHEL4 | | `qt` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.3.3-11.RHEL4 | | `qt-MySQL` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.3.3-11.RHEL4 | | `qt-ODBC` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.3.3-11.RHEL4 | | `qt-PostgreSQL` | Red Hat:enterprise_linux:4::desktop | All versions | 1:3.3.3-11.RHEL4 | Products: Trolltech Qt. ## How do I fix CVE-2007-3388? Upgrade to a fixed version. ## Is CVE-2007-3388 being exploited? There is no known exploitation of CVE-2007-3388 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2007-4137](https://insights.sbomify.com/CVE-2007-4137/): Memory corruption in n/a (high 7.5) - [CVE-2004-0691](https://insights.sbomify.com/CVE-2004-0691/): Memory corruption in n/a (high 7.5) - [CVE-2004-0692](https://insights.sbomify.com/CVE-2004-0692/): Null dereference in n/a (medium 5.0) - [CVE-2004-0693](https://insights.sbomify.com/CVE-2004-0693/): Null dereference in n/a (medium 5.0) - [CVE-2005-0627](https://insights.sbomify.com/CVE-2005-0627/): Path traversal in n/a (medium 4.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2007-3388 and fix it if it is affected. What it is: CVE-2007-3388 is a medium-severity code injection vulnerability in n/a, published on 3 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2007-3388 in the wild and no public exploit code. Affected product: n/a. 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-2007-3388/ (Markdown: https://insights.sbomify.com/CVE-2007-3388/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-3388 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-3388 - OSV: https://osv.dev/vulnerability/CVE-2007-3388 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-3388/ Summaries are generated and may contain mistakes; the official description above is the record.