CVE-2024-7014
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEvilVideo vulnerability allows sending malicious apps disguised as videos in Telegram for Android application affecting versions 10.14.4 and older.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceEvilVideo is a vulnerability in Telegram for Android (versions 10.14.4 and older) that allows attackers to send malicious applications disguised as video files. The attack exploits how Telegram handles certain file types and their associated metadata, enabling the delivery of malicious APKs that appear to users as video content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.14.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm you are using Telegram for AndroidNavigate to Settings > About on your Telegram app. Verify the platform listed is Android, not iOS or another platform. This CVE only affects the Android version.Affected if The platform is Android
-
Check your Telegram for Android version numberIn the Telegram app, go to Settings > About. Note the version number displayed (for example, it may show something like 10.14.4 or 10.14.5).Affected if You cannot determine the version number from the app settings
-
Compare your installed version to the affected rangeCompare the version number you found against the vulnerable range: versions older than 10.14.5 are affected. If your version shows 10.14.4 or lower, you are in the affected range. If it shows 10.14.5 or higher, you are not in the affected range.Affected if Your installed version is less than 10.14.5 (for example, 10.14.4, 10.14.3, etc.)
You are affected if you are running Telegram for Android version 10.14.4 or older.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.14.5
Update Telegram for Android to a version newer than 10.14.4. Users should exercise caution when receiving unexpected video files and verify sender identity before downloading any media.
Telegram for Android 10.14.5
- Open the Google Play Store on your Android device
- Search for "Telegram" in the app store
- Locate the official Telegram app in the search results
- Tap the "Update" button to update to the latest version
- Ensure the updated version is 10.14.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7014 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data