# CVE-2013-0254: Information disclosure in n/a

> Local attackers can read or modify sensitive data in Qt shared memory segments due to weak permissions, potentially exposing information or altering program state.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g639-7h38-4849, RHSA-2013:0669

## What is CVE-2013-0254?

CVE-2013-0254 is a low-severity vulnerability in Qt Qt, published on 6 Feb 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The QSharedMemory class in Qt 5.0.0, 4.8.x before 4.8.5, 4.7.x before 4.7.6, and other versions including 4.4.0 uses weak permissions (world-readable and world-writable) for shared memory segments, which allows local users to read sensitive information or modify critical program data, as demonstrated by reading a pixmap being sent to an X server.

Weakness: CWE-264

## Which versions are affected by CVE-2013-0254?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phonon-backend-gstreamer` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-demos` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-devel` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-doc` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-examples` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-mysql` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-odbc` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-postgresql` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-sqlite` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `qt-x11` | Red Hat:enterprise_linux:6::client | All versions | 1:4.6.2-26.el6_4 |
| `phonon-backend-gstreamer` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-demos` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-examples` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-mysql` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-odbc` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-postgresql` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-sqlite` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `qt-x11` | Red Hat:enterprise_linux:6::computenode | All versions | 1:4.6.2-26.el6_4 |
| `phonon-backend-gstreamer` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-demos` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-devel` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-doc` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-examples` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-mysql` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-odbc` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-postgresql` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-sqlite` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `qt-x11` | Red Hat:enterprise_linux:6::server | All versions | 1:4.6.2-26.el6_4 |
| `phonon-backend-gstreamer` | Red Hat:enterprise_linux:6::workstation | All versions | 1:4.6.2-26.el6_4 |
| `qt` | Red Hat:enterprise_linux:6::workstation | All versions | 1:4.6.2-26.el6_4 |
| `qt-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 1:4.6.2-26.el6_4 |
| `qt-demos` | Red Hat:enterprise_linux:6::workstation | All versions | 1:4.6.2-26.el6_4 |

Products: Qt Qt.

## How do I fix CVE-2013-0254?

Upgrade to a fixed version.

## Is CVE-2013-0254 being exploited?

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

## Other vulnerabilities in Qt Qt

- [CVE-2020-12267](https://insights.sbomify.com/CVE-2020-12267/): Use after free in n/a (critical 9.8)
- [CVE-2017-10904](https://insights.sbomify.com/CVE-2017-10904/): Command injection in Qt for Android (critical 9.8)
- [CVE-2011-3194](https://insights.sbomify.com/CVE-2011-3194/): Memory corruption in n/a (critical 9.3)
- [CVE-2022-40983](https://insights.sbomify.com/CVE-2022-40983/): Integer overflow in Qt (high 8.8)
- [CVE-2022-43591](https://insights.sbomify.com/CVE-2022-43591/): Memory corruption in Qt (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0254 and fix it if it is affected.

What it is: CVE-2013-0254 is a low-severity vulnerability in Qt Qt, published on 6 Feb 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0254 in the wild and no public exploit code.

Affected product: Qt Qt. 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-2013-0254/ (Markdown: https://insights.sbomify.com/CVE-2013-0254/index.md)
```

## Sources

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

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