dbcve.org
Flexnet PublisherApplication · Flexerasoftware

CVE-2015-8277

CRITICAL · 9.8 CVSS v3.0 Published 2016-02-24
Fix available
A fix is available. Upgrade to after 11.13.1.0 or later.
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
Multiple buffer overflows in (1) lmgrd and (2) Vendor Daemon in Flexera FlexNet Publisher before 11.13.1.2 Security Update 1 allow remote attackers to execute arbitrary code via a crafted packet with opcode (a) 0x107 or (b) 0x10a.

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 vulnerabilities in Flexera FlexNet Publisher's lmgrd and Vendor Daemon components allow remote attackers to execute arbitrary code via crafted packets using opcodes 0x107 or 0x10a. The vulnerability exists in versions prior to 11.13.1.2 Security Update 1 and is exploitable without authentication.

MitigationApply vendor patch by updating FlexNet Publisher to version 11.13.1.2 Security Update 1 or later. If immediate patching is not possible, consider network segmentation to restrict access to license manager ports.

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
Flexnet PublisherApplication
Affected:<= 11.13.1.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 checks

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

  1. Identify FlexNet Publisher installation and version
    Check for FlexNet Publisher installation directory (common paths: C:\Program Files\FlexNet Publisher or /opt/flexnet) and locate lmgrd.exe or vendor daemon binaries. Right-click the executable, select Properties, and check the Version tab for the product version.
    Affected if The installed version is 11.13.1.0 or earlier, or the version cannot be determined but the software is present.
  2. Confirm lmgrd service is running
    On Windows, open Services console (services.msc) and look for 'FlexNet Publisher License Manager' or check Task Manager for lmgrd.exe process. On Linux, run 'ps -ef | grep lmgrd' to list running license manager processes.
    Affected if The lmgrd service or process is actively running on the system.
  3. Identify Vendor Daemon processes
    Run Task Manager (Windows) or 'ps -ef' (Linux) and look for vendor daemon processes, typically named after the software vendor (e.g., 'acrotrt', 'magics', or generic 'vendor' processes in the FlexNet directory).
    Affected if Vendor daemon processes associated with FlexNet Publisher are running.
  4. Check network exposure of license manager ports
    Open command prompt and run 'netstat -ano | findstr "27000"' (default FlexNet port) or use 'netstat -an' to list all listening ports. Verify if ports 27000-27009 or custom license ports are bound to 0.0.0.0 or accessible from external IPs.
    Affected if License manager ports are listening on external interfaces (0.0.0.0) or the system is directly accessible from untrusted networks.

The system is affected if FlexNet Publisher version 11.13.1.0 or earlier is installed and the lmgrd/vendor daemon services are running and exposed on the network.

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
Upgrade available Upgrade to a release after 11.13.1.0
Interim mitigation

Apply vendor patch by updating FlexNet Publisher to version 11.13.1.2 Security Update 1 or later. If immediate patching is not possible, consider network segmentation to restrict access to license manager ports.

Recommended fix High confidence

FlexNet Publisher 11.13.1.2 Security Update 1

  1. 1. Identify the current FlexNet Publisher version by checking the lmgrd and Vendor Daemon components
  2. 2. Navigate to the Flexera/Citrix support portal and locate FlexNet Publisher 11.13.1.2 Security Update 1
  3. 3. Download the security update package for your platform (Windows or Linux)
  4. 4. Back up the existing FlexNet Publisher installation directory and configuration files
  5. 5. Stop all running FlexNet services (lmgrd and Vendor Daemon)
  6. 6. Apply the 11.13.1.2 Security Update 1 by running the installer or extracting the patch
  7. 7. Restart the FlexNet services and verify version 11.13.1.2 is running
  8. 8. Test that license checkout and management functionality operates normally
Caveat Review release notes for any configuration or feature changes between 11.13.1.0/11.13.1.1 and 11.13.1.2 Security Update 1 before upgrading

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

Fix this in Flexnet Publisher Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,660
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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