dbcve.org
JunosOperating system · Juniper

CVE-2013-4685

HIGH · 10.0 CVSS v2.0 Published 2013-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer overflow in flowd in Juniper Junos 10.4 before 10.4S14, 11.4 before 11.4R7, 12.1 before 12.1R6, and 12.1X44 before 12.1X44-D15 on SRX devices, when Captive Portal is enabled with the UAC enforcer role, allows remote attackers to execute arbitrary code via crafted HTTP requests, aka PR 849100.

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 confidence

Buffer overflow vulnerability in the flowd daemon in Juniper Junos on SRX devices allows remote attackers to execute arbitrary code via crafted HTTP requests when Captive Portal is enabled with the UAC (Unified Access Control) enforcer role. The vulnerability affects multiple version branches including 10.4 before 10.4S14, 11.4 before 11.4R7, 12.1 before 12.1R6, and 12.1X44 before 12.1X44-D15.

MitigationUpgrade Junos to the specified minimum version (10.4S14, 11.4R7, 12.1R6, or 12.1X44-D15) or later. If immediate patching is not feasible, disable Captive Portal or remove the UAC enforcer role configuration to eliminate the attack surface.

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
JunosOperating system
Affected:= 10.4= 11.4= 12.1= 12.1x44
Srx100Hardware / appliance
Affected:all versions
Srx110Hardware / appliance
Affected:all versions
Srx1400Hardware / appliance
Affected:all versions
Srx210Hardware / appliance
Affected:all versions
Srx220Hardware / appliance
Affected:all versions
Srx240Hardware / appliance
Affected:all versions
Srx3400Hardware / appliance
Affected:all versions

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the SRX device model
    Run 'show chassis hardware' or check the device model via 'show system information' to confirm it is an SRX100, SRX110, SRX1400, SRX210, SRX220, SRX240, or SRX3400
    Affected if Device is any of these SRX models running any version - they are all listed as affected
  2. Determine the installed Junos version
    Run 'show version' or 'show system information' to retrieve the exact Junos version string (for example, 10.4R1, 12.1R3, etc.)
    Affected if Version is 10.4 before 10.4S14, 11.4 before 11.4R7, 12.1 before 12.1R6, or 12.1X44 before 12.1X44-D15
  3. Verify if Captive Portal is enabled
    Run 'show services captive-portal status' or check the configuration under 'set services captive-portal' hierarchy using 'show configuration | match captive-portal'
    Affected if Captive Portal is actively enabled (not just configured but actually operational)
  4. Confirm the UAC enforcer role is configured
    Check the configuration for UAC enforcer role by running 'show configuration | match enforcer' or examining 'set services unified-access-control' configuration hierarchy
    Affected if UAC (Unified Access Control) enforcer role is configured in the Captive Portal settings

Device is affected if it is an SRX model (100/110/1400/210/220/240/3400) running a vulnerable Junos version AND has Captive Portal enabled with the UAC enforcer role configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos to the specified minimum version (10.4S14, 11.4R7, 12.1R6, or 12.1X44-D15) or later. If immediate patching is not feasible, disable Captive Portal or remove the UAC enforcer role configuration to eliminate the attack surface.

Recommended fix High confidence

10.4S14, 11.4R7, 12.1R6, or 12.1X44-D15 (depending on current branch)

  1. Identify the current Junos version running on the SRX device using 'show version'
  2. Determine which Junos branch is currently in use (10.4, 11.4, 12.1, or 12.1X44)
  3. If using Junos 10.4 branch, upgrade to version 10.4S14 or later
  4. If using Junos 11.4 branch, upgrade to version 11.4R7 or later
  5. If using Junos 12.1 branch, upgrade to version 12.1R6 or later
  6. If using Junos 12.1X44 branch, upgrade to version 12.1X44-D15 or later
  7. After upgrade, verify the new version is installed using 'show version'
  8. If Captive Portal with UAC enforcer role is no longer needed, disable it to reduce attack surface
Caveat Standard Junos upgrade procedures apply; ensure configuration backup before upgrade; some functionality changes may occur between major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4685 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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