CVE-2013-0254: 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…
Noroxi assessment
Priority: Monitor (action score 14/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.43% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: qt4-x11 (Debian:6.0) 4:4.6.3-4+squeeze3; phonon-backend-gstreamer (Red Hat:enterprise_linux:6::client) 1:4.6.2-26.el6_4; qt (Red Hat:enterprise_linux:6::client) 1:4.6.2-26.el6_4.
Low priority for now. Upgrade to qt4-x11 (Debian:6.0) 4:4.6.3-4+squeeze3; phonon-backend-gstreamer (Red Hat:enterprise_linux:6::client) 1:4.6.2-26.el6_4; qt (Red Hat:enterprise_linux:6::client) 1:4.6.2-26.el6_4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 6, 2013
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-264
Report tools
Action score
14
Low priority for now.
- CVSS
- 14 / 40 · 3.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qt | qt | cpe:2.3:a:qt:qt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qt qt1.41
- qt qt1.42
- qt qt1.43
- qt qt1.44
- qt qt1.45
- qt qt2.0.0
- qt qt2.0.1
- qt qt2.0.2
+12 more rows
- qt qt3.3.0
- qt qt3.3.1
- qt qt3.3.2
- qt qt3.3.3
- qt qt3.3.4
- qt qt3.3.5
- qt qt3.3.6
- qt qt4.0.0
- qt qt4.0.1
- qt qt4.1.0
- qt qt4.1.1
- qt qt4.1.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | qt4-x11 | before 4:4.6.3-4+squeeze3 | 4:4.6.3-4+squeeze3 |
| Red Hat:enterprise_linux:6::client | phonon-backend-gstreamer | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-debuginfo | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-demos | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-devel | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-doc | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-examples | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-mysql | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-odbc | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-postgresql | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-sqlite | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
| Red Hat:enterprise_linux:6::client | qt-x11 | before 1:4.6.2-26.el6_4 | 1:4.6.2-26.el6_4 |
Same product
qt: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12267setMarkdown in Qt before 5.14.2 has a use-after-free related to QTextMarkdownImporter::insertBlock.40Plan
- CVE-2018-19873An issue was discovered in Qt before 5.11.3.40Plan
- CVE-2017-10904Qt for Android prior to 5.9.0 allows remote attackers to execute arbitrary OS commands via unspecified vectors.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2011-3194Jun 15, 2012 · Buffer overflow in the TIFF reader in gui/image/qtiffhandler.cpp in Qt 4.7.4 allows remote attackers to cause a denial of service (crash)…39Monitor
- ← EarlierCVE-2010-5076Jun 29, 2012 · QSslSocket in Qt before 4.7.0-rc1 recognizes a wildcard IP address in the subject's Common Name field of an X.509 certificate, which might…17Monitor
- Later →CVE-2012-5624Feb 24, 2013 · The XMLHttpRequest object in Qt before 4.8.4 enables http redirection to the file scheme, which allows man-in-the-middle attackers to force…18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:qt4-x11 | 4:4.6.3-4+squeeze3 · Debian:6.0 | Package registry (OSV) |
| red hat:phonon-backend-gstreamer | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-debuginfo | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-demos | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-devel | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-doc | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-examples | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-mysql | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-odbc | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-postgresql | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-sqlite | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:qt-x11 | 1:4.6.2-26.el6_4 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:L/AC:L/Au:N/C:P/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.