dbcve.org
Verastream Host IntegratorApplication · Attachmate

CVE-2013-3626

HIGH · 9.3 CVSS v2.0 Published 2013-11-06
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
Directory traversal vulnerability in the Session Server in Attachmate Verastream Host Integrator (VHI) 6.0 through 7.5 SP 1 HF 1 allows remote attackers to upload and execute arbitrary files via a crafted message.

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

Directory traversal vulnerability in the Session Server of Attachmate Verastream Host Integrator (VHI) versions 6.0 through 7.5 SP1 HF1 allows remote attackers to craft malicious messages that bypass path validation, enabling upload and execution of arbitrary files on the target system.

MitigationApply vendor patches or hotfixes for this vulnerability immediately and restrict network access to the Session Server to mitigate remote exploitation.

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
Verastream Host IntegratorApplication
Affected:= 6.0= 6.5= 6.6= 7.0= 7.1= 7.5

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 if Verastream Host Integrator is installed
    Look for Attachmate VHI installation directories (commonly under C:\Program Files\Attachmate\Verastream or similar). Check Windows Services for 'Verastream Host Integrator' or 'VHI' services.
    Affected if VHI software is found installed on the system
  2. Determine the installed VHI version
    Check the version information in the installation directory, or use the VHI Administration Tool to view the product version. Compare against affected versions 6.0, 6.5, 6.6, 7.0, 7.1, and 7.5.
    Affected if Installed version falls within 6.0 through 7.5 SP1 HF1
  3. Verify Session Server component status
    Check if the Session Server service (often named 'Host Integrator Session Server' or similar) is running. Use Services.msc or command 'sc query' to check service status.
    Affected if Session Server service is running and enabled
  4. Check network exposure of Session Server
    Review firewall rules and network configuration to determine if the Session Server port (default VHI port 9929/tcp or configured port) is exposed to untrusted networks.
    Affected if Session Server port is accessible from untrusted/networked systems
  5. Inspect Session Server configuration
    Examine the VHI Session Server configuration files (typically in the config subdirectory of the VHI installation) for allowed message handlers and file upload settings.
    Affected if File upload handlers or message processing features are enabled in Session Server config

A system is affected if Verastream Host Integrator versions 6.0-7.5 SP1 HF1 are installed with the Session Server running and network-accessible, allowing remote attackers to send crafted traversal messages.

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

Apply vendor patches or hotfixes for this vulnerability immediately and restrict network access to the Session Server to mitigate remote exploitation.

Recommended fix Moderate confidence

VHI 7.5 SP 1 HF 2 or later (contact vendor for exact fixed version)

  1. 1. Contact Attachmate/Riverbed support at support.attachmate.com to obtain the specific patch or hotfix for CVE-2013-3626
  2. 2. Request VHI version 7.5 SP 1 HF 2 or later which contains the fix for the directory traversal vulnerability
  3. 3. Download the patch/hotfix from the official support portal
  4. 4. Back up your current VHI configuration and database
  5. 5. Apply the patch following the provided installation instructions
  6. 6. Restart the Session Server service to ensure the patch takes effect
  7. 7. Verify the fix by checking that the Session Server is operational and test file upload functionality
Caveat Review release notes for any configuration changes required when applying the hotfix

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

Fix this in Verastream Host Integrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3626 — 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-3626 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