CVE-2017-1000034
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 · uneditedAkka versions <=2.4.16 and 2.5-M1 are vulnerable to a java deserialization attack in its Remoting component resulting in remote code execution in the context of the ActorSystem.
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 confidenceAkka versions 2.4.16 and earlier, along with 2.5-M1, contain a java deserialization vulnerability in the Remoting component. This flaw allows remote attackers to execute arbitrary code by sending maliciously crafted serialized Java objects to the ActorSystem through the remoting interface.
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.4.16= 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/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.
-
Identify installed Akka versionCheck your project dependencies (Maven pom.xml, sbt build file, or Gradle build.gradle) for the akka-actor dependency version. If running a deployed application, check the akka-actor JAR manifest or the version included in your classpath.Affected if The installed version is 2.4.16 or earlier, or exactly 2.5-M1 (milestone 1)
-
Confirm Akka Remoting is enabledExamine your Akka configuration files (application.conf) for any remoting-related settings. Look for sections containing 'akka.remote' or 'akka.actor.remote'. Check for configurations such as 'enabled = true' under remoting settings, or the presence of 'NettyRemoteTransport' or 'TcpRemoteTransport' in the configuration.Affected if Akka Remoting is explicitly enabled in the configuration with the remoting transport actively configured
-
Verify remoting bind address is exposedInspect the 'akka.remote.bind.hostname' or 'akka.remote.hostname' configuration values. Check if the system is bound to a non-localhost IP address or 0.0.0.0, which would accept remote connections.Affected if The bind address is set to a reachable network interface (not 127.0.0.1/localhost), exposing the remoting port to network traffic
-
Identify exposed remoting portsReview configuration for 'akka.remote.bind.port' or 'akka.remote.port' values. Check running process ports using netstat or similar tools to identify which ports the Akka actor system is listening on for remoting.Affected if Remoting ports are listening and accessible from untrusted network segments
You are affected if your Akka version is 2.4.16 or earlier (or exactly 2.5-M1) AND Akka Remoting is enabled with the bind address exposed to network access.
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 Akka to version 2.4.17 or later (or a stable 2.5.x release) to remediate this vulnerability. If immediate patching is not possible, disable or restrict Akka Remoting and ensure network access to remoting ports is limited to trusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000034 — 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-2017-1000034 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