CVE-2018-15122
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 · uneditedAn issue found in Progress Telerik JustAssembly through 2018.1.323.2 and JustDecompile through 2018.2.605.0 makes it possible to execute code by decompiling a compiled .NET object (such as DLL or EXE) with an embedded resource file by clicking on the resource.
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 confidenceTelerik JustAssembly and JustDecompile contain a code execution vulnerability when decompiling malicious .NET assemblies with embedded resources. Clicking on an embedded resource in a specially crafted DLL or EXE triggers arbitrary code execution, allowing an attacker to run commands on the victim's machine.
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>= 2018.1.323.2>= 2018.2.605.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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.
-
Check if Telerik JustAssembly is installedLook for JustAssembly in the system (typically in Program Files or a user's AppData folder) and identify its version numberAffected if The installed version is 2018.1.323.2 or higher and you open a specially crafted .NET assembly with embedded resources
-
Check if Telerik JustDecompile is installedLook for JustDecompile in the system (typically in Program Files or a user's AppData folder) and identify its version numberAffected if The installed version is 2018.2.605.0 or higher and you open a specially crafted .NET assembly with embedded resources
-
Determine usage patterns with untrusted assembliesReview whether JustAssembly or JustDecompile is used to open assemblies from untrusted or unknown sources, particularly DLL or EXE files that may contain embedded resourcesAffected if You regularly decompile assemblies from untrusted or unknown origins using these tools
-
Identify if clicking on embedded resources occursWhen using these tools, note whether the workflow involves clicking on or interacting with embedded resources within decompiled assembliesAffected if Your typical workflow involves clicking on embedded resources in assemblies opened with these tools
You are affected if you have JustAssembly version 2018.1.323.2 or higher, or JustDecompile version 2018.2.605.0 or higher, and you open specially crafted malicious .NET assemblies and interact with embedded resources in them.
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 dataUpdate Telerik JustAssembly to a version after 2018.1.323.2 and JustDecompile to a version after 2018.2.605.0, or avoid opening untrusted .NET assemblies with these tools until patches are applied.
- Consultation3.0 h
- Implementation2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15122 — 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-2018-15122 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