CVE-2012-4005
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 · uneditedThe NHN Japan NAVER LINE application before 2.5.5 for Android does not properly handle implicit intents, which allows remote attackers to obtain sensitive message information via a crafted application.
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 · high confidenceThe NAVER LINE Android application before version 2.5.5 did not properly restrict implicit intent handling, allowing any application on the device to send intents that the LINE app would process. A malicious app could exploit this to intercept sensitive message information by sending crafted intents that triggered the vulnerable app to return message data.
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<= 2.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Identify LINE application package nameRun 'adb shell pm list packages | grep -i line' to find the LINE package name (typically jp.naver.line.android)Affected if The package is not found (app not installed) or version cannot be determined
-
Retrieve installed LINE versionRun 'adb shell dumpsys package <package_name>' and look for versionName and versionCode in the package information outputAffected if The version returned is blank or cannot be parsed
-
Compare version against vulnerable rangeCompare the installed versionName to the affected range: any version <= 2.5 (such as 2.5, 2.4.x, 2.3, etc.) is vulnerableAffected if The installed version is 2.5 or any earlier version (e.g., 2.4.1, 2.3.0, 1.x)
-
Verify intent broadcast receiver exposure (optional)Run 'adb shell dumpsys package <package_name> | grep -A 20 IntentReceiver' to list registered intent receivers; check if sensitive actions (e.g., message handling) lack permission constraintsAffected if Sensitive intent receivers do not require permissions and accept intents from any source
A user is affected if the LINE Android application version is 2.5 or earlier, since these versions accept intents from any application without validation.
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.
From vendor dataUpgrade to LINE application version 2.5.5 or later, which properly validates and restricts intent sources. For third-party applications, implement explicit intent declarations and/or permission-based intent filtering to prevent unauthorized apps from sending sensitive intents.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4005 — 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-2012-4005 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