FlexNet Publisher Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Description The help contents packaged with lmadmin 11.6.4.0 are incorrect. This was reported as known issue FNP-21453.  Replication Scenario No replication steps required. Workaround No workaround available.  Version Fix Target FlexNet Publisher lmadmin 2019 R2 SP1 (11.16.4.1)  Resolution Please upgrade the lmadmin to 11.16.4.1. From this version, the correct help contents will display in the lmadmin server UI.  
View full article
Question: Why doesn't "lmvminfo -long" return detailed virtualization details? Answer: The lmvminfo utility returns the environment as virtual or not and possibly additional details in the case of a virtual environment with (-long) switch.  Usage: lmutil lmvminfo [-long]   Where lmvminfo returns the following: lmvminfo - Copyright (c) 1989-2018 Flexera. All Rights Reserved. Running on Physical Platform   lmvminfo - Copyright (c) 1989-2018 Flexera. All Rights Reserved. Running on Virtual Platform   Where -long returns the following: Family of the virtual machine. The Family generally denotes the provider of the detected hypervisor software that the virtual machine (VM) is running on. Name of the virtual machine. The Name specifies the detected hypervisor product that the virtual machine (VM) is running on. The Name is for future use and is intended to be a subset of family. UUID of the machine GENID of the machine   FlexNet Licensing Service Dependency Depending on the version of lmvminfo and the underlying licensing release (FNP version) the retrieval of virtual machine information (such as UUID) is either done by the core licensing software or the "FlexNet Licensing Service" component - either FNLS on Windows or a new Daemon introduced in 11.14.1 on Linux.  (We will refer to this as “FNLS” for simplicity). Recent releases (post 11.14.x) require that “FNLS” be installed to obtain VM details. If you haven’t installed “FNLS” an error will be returned when using “-long”. The actual error message will depend on the licensing version (FNP and lmvminfo) in use.  Here are some examples of what you might receive as output of the lmvminfo –long command:   Pre-11.14.0.1 (Windows) lmvminfo - Copyright (c) 1989-2014 Flexera Software LLC. All Rights Reserved. Running on Virtual Platform FAMILY=MICROSOFT NAME=HYPERV UUID=9738F8AB-027F-4D3C-A9BF-BE65367786F5 GENID: ERROR - Unavailable. Insufficient privilege. Error: FNP License Service not installed   FNP 11.16.x (Windows) lmutil - Copyright (c) 1989-2019 Flexera. All Rights Reserved. The FlexNet Licensing Service is not installed.  (-213,0)   NOTE:  Before changes implemented in 11.14.0.1 (Windows) and 11.14.1 (Linux) the core FNP code was checking for the existence of virtual machines.  In the first example above, you will notice that UUID was returned despite the fact that “FNLS” was not installed (as evident by the error message).  The error message has been refined in subsequent releases, based on user feedback. In the second example, the retrieval of VM information is done in “FNLS” and the only thing displayed when “FNLS” is not installed is the error informing you of that condition. The reason for moving the virtualization checking from the main code to the service  was to improve performance.  It is expected that going forward you will need to have the “FNLS” service (Windows) or Daemon (Linux) installed for lmvminfo – long to provide the full VM details.  NOTE:  We may from time to time introduce additional functionality in this service, so be sure to watch Release Notes.
View full article
This article will explain the steps needed to configure a FlexNet Publisher toolkit to use a combined Vendor Defined HostID and Composite HostID on Windows.
View full article
This article will explain the steps needed to configure a FlexNet Publisher toolkit to use a combined Vendor Defined HostID and Composite HostID on Linux.
View full article
Question: How can we fetch the version of dongle driver version, installed on the local system? Answer: For HASP: -  hasplms -v hasplms version 19.0.1.63692 And the package shown in here: haspdinst.exe -info For WIBU: - Query the registry location "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WIBU-SYSTEMS\WIBU-KEY\General\CurrentVersion\Version" OR  - Once the dongle driver is installed, run the executable named Wku32.exe (on Windows - C:\Program Files (x86)\WIBUKEY\Bin) and under Linux and MacOS "wku".  Output from Windows:  C:\Program Files (x86)\WIBUKEY\Bin>wku32.exe  wku32 - WibuKey User Universal Support Tool.  wku32 Version 6.51 of 2019-Apr-02 (Build 3477) for Win32.  Copyright (C) 1994-2019 by WIBU-SYSTEMS AG, www.wibu.com. All rights reserved.  Available WibuKey ports at local computer:  [Calling Driver: Version 6.51 of Apr/02/2019]  [Kernel Driver: Version 6.50a of Jan/08/2019]  0 WibuKey ports scanned: 0 WibuBoxes at 0 ports found. 
View full article
Question: What FLEXLM_BORROWFILE environment variable is and how can it be used? Answer: FLEXLM_BORROWFILE is an environment variable, which if set, the path/file set under it is considered as the location to save the borrow cache for Flexnet Publisher borrow functionality. Windows FNP toolkit needs the file name provided in environment variable to be available under "SOFTWARE\\FLEXlm License Manager" i.e. appends the environment variable entry to the hard coded file location (there is no way to bypass or change that- at utility level). Since borrow code on Linux and Windows are different, Linux accepts an absolute file path whereas windows doesn’t. For Windows, we would need to create a key under "SOFTWARE\\FLEXlm License Manager\flexborrow”, specify particular name under FLEXLM_BORROWFILE (= flexborrow) and it works fine then after.
View full article
Summary Does FNP implement a FIPS 140-2 compliant encryption method? Question Does the license server code implement a FIPS 140-2 compliant encryption method? http://en.wikipedia.org/wiki/FIPS_140-2   Answer FlexNet Publisher is not in compliance with the FIPS standard. We have no plans to make FlexNet Publisher compatible or be in compliance with FIPS-140. Please note that all the cryptography in FlexNet Licensing is used to protect the license rights granted by the provider to their customers. None of the cryptography is used to protect the provider's customers' data. If the only reason a provider is asking this question is because they have certain obligations when protecting their customers' data, FlexNet Licensing's cryptography is not used for that purpose and thus the certification level of FlexNet Licensing's cryptography is not relevant.
View full article
Question: Flexnet Error -63 (LM_NOTLICDMIN) in license checkout. Not a documented *possible* return code. Answer: This error can be seen only in specific conditions: - Performing Server reread from a non admin console/account and when server was started with a restrictive privilege for server reread. (-x Lmreread) - Performing client removal (lmremove) from a non admin console/account, when server was started with a restrictive privilege for lmremove. (-x lmremove) - Trying to shutdown the server from a non admin console/account, if server was with a restrictive privilege for server shutdown. (-x lmdown) - If server was started with “-2 -p” and presumably “-local”, then this error will be seen by clients, if they are not a part of “lmadmin” group. Here lmadmin group means, a Unix group called “lmadmin” Solution: Create a UNIX group called ‘lmadmin’ and add particular user to that group. For windows, if the operation was not initiated with LOCALSYSTEM privilege. Solution: Try running the operation with the reference of attached batch file. Rename it to “.bat extension”. ALSO This error will be seen, if a particular user doesn’t have enough privilege to query the windows registry details. While performing the checkout operation, the client application queries the registry for “SOFWARE\\FLEXlm License Manager”, to get the VENDOR_LICENSE_FILE details (as well as for other operations).  When client tries to open a handle with specific query key (RegOpenKeyEx), and in case the operation fails - then for specific error of “ERROR_ACCESS_DENIED” (returned by windows), FNP sets this error i.e. (-63, 403). 
View full article
Question: ERROR OBSERVATION: No PID file for FNPLicensingService 1.) Why does this error mean? 2.)  What is the significance of this PID file? 3.) Is it ok to ignore the existence of this file 4.) What are the probable root cause of this observation? Answer: 1.)  this error is seen because the FNPLicensingService is not properly started on the machine 2.)  FNPLicensingService.pid contains the processID of the FNPLicensingService. 3.)  he above error signifies the FNPLicensingService is not properly installed.  i think FNPLicensingService daemon is not active, So we cannot ignore the existence of this file. 4.) This error is generally seen in case if appropriate bit of FUSE libraries are not installed. For installing 32 bit FNLS, ensure that 32 bit of FUSE libraries are installed and same goes for 64 bit FNLS (i.e. 64 bit FUSE) Also,  var/run/FNP directory is getting deleted after restarting/fresh installation the machine (on latest Non windows)and FNPLicensingService is not able to create the var/run/FNP/FNPLicensingService64.pid file.  workaround:  ***********  create /var/run/FNP directory and run the installer again. 
View full article
Question: Has older HASP (HASP4) dongle support removed from latest version of FNP toolkits? Answer: Starting 11.14.0 we have to enable support for the HASP4 dongles in the daemon configuration file ls_vendor.c (unsigned int ls_flexid9_hasp4_support = 1;) .  After doing that and ensuring that we build the toolkit with additional argument as DONGLE=1, with a clean build, we should be able to start the vendor daemon. 
View full article
Question: Can a Publisher attach Flexera Product Documents in its distribution? Answer: The answer is that it is permissible to re-distribute the documentation in its original form, unmodified in any way. The means of distribution can include: Bundling it into their software, and distributing it by a physical medium such as DVD Bundling it into their software and delivering it by electronic means from a server (as long as access to the server is protected by an account with adequately secure user name and password): By some mechanism that pushes the software out to customers By allowing customers to download the software Make the document available on its own, by the same mechanisms as above.
View full article
Question: Clarification of what files can be re-distributed to end users? Answer: As far as sharing the toolkit executable or libraries are concerned, we have a detailed section about it in latest version of FNP product document. To be precise Chapter-8 of fnp_devenv.pdf (Development Environment Guide)*(Distributing the FlexEnabled Application for License File–Based Licensing). Similarly for trusted storage based licensing the details is available in Chapter 6(Distributing the FlexEnabled Application for Trusted Storage–Based Licensing). I am attaching a copy of it for your reference.  In general, there are four categories of executables that can be considered for redistribution.  1.) Executables generated from building makefile and makefile.act, minus lmcrypt, preptool and tsreset can be shared  2.) executables that must be redistributed in order for licensing to work (lmgrd or lmadmin, VD and client application, plus lmstat. For TS applications additionally: FNP_Act_Installer.dll (from which FlexNet Licensing Service is installed), activation applications for server and client TS and the libFNP.dll that is the output of prepping.  3.) executables that are generated from example source code provided in the kit. Any of these can be redistributed - if the example is sufficient for producers requirements. Producers are of course fully entitled to modify example source code, then rebuild and produce their own versions of example utilities. Executables in this category include installs.exe and activation applications like app/servercomptranutil.  4.) executables that are typically only redistributed in support scenarios (tsactdiags, tsreset).  Note: installs.exe is a command-line tool used for installing lmgrd as a Windows service, including setting up a dependency on the FlexNet Licensing Service if TS licensing is involved. Alternatives to installs.exe include  lmtools - a windows GUI app - Can be Shared.   
View full article
Question: Over the years, our customers have had  issues with LSB-loader as described in FNP release documentations. Moreover,  on some recent Linux updates, such as SUSE Enterprise Linux 12, the LSB component is not offered as part of the supported distribution. Components in FlexNet Publisher, such as lmgrd, require the LSB-loader. If this is not present, lmgrd will fail to run with a 'file not found' error (FNP-11338, FNP- 11353) Answer: Starting FNP-11.14 tookit, The   install_fnp.sh   will now issue a warning if it detects LSB is not installed on the host: $ sudo ./install_fnp.sh ... Checking LSB compatibility... *** WARNING: 64-bit LSB packages not installed LSB compatibility checks complete ... FNP utilities will continue to give the   File not found   error. Supplying the   --nolsb   flag to the command will cause fake symlinks to be created to mimic the missing LSB installation: $ sudo ./install_fnp.sh --nolsb ... Checking LSB compatibility... *** WARNING: 64-bit LSB packages not installed Fix attempted by creating symlink for /lib64/ld-lsb-x86-64.so.3 LSB compatibility checks complete ... After which FNP utilities should run ok.
View full article
JIRA ISSUE: FNP-11299, FNP-11300, FNP-20479 Issue:  1.) Reservation line is not displaying in server log when RESERVE and MAX are both in options file. 2.) License exceeds count message is coming instead of MAX line in serverlog when both MAX and RESERVE is kept in options file. Workaround: We must place MAX statement before RESERVE in options file for it to work correctly.
View full article
Question: I read in a 11.14.0 release note that SIGN2 keyword is deprecated, but  SIGN= is seen as the original public key signature system and SIGN2= the new improved system. So if I remove SIGN2 the license will not be less secured ?  Answer: ) SIGN2 will be used in license file to support old clients which are built with different algorithm. ) Presently, We have two algorithms to generate the sign value in license file:- TRL1 which is deprecated now and TRL2 is the enhanced and latest version with understanding as more robust to crack. ) Consider old client is built with TRL1. In that case, we need to mention both the SIGN keywords and each will have exclusive sign value related to particular TRL key. ) If there is just one SIGN keyword mentioned in FEATURE line then default SIGN value will be enhanced one and on the basis of TRL2 algorithm. ) As there is expectation that all the publishers should move to more secured algorithm(TRL2) with time, it diminishes the need of extra SIGNs in feature line. If we have only one SIGN value(it means SIGN) as part of license file then it is with TRL2 and linked to SIGN. But    But if two SIGN values(it means SIGN,SIGN2) are required to be part of license file then SIGN will get TRL1 value and SIGN2 will get TRL2 value. Also, below details should help you have more understanding on this case.   Signature Configuration #1 #2 #3 #4 #5 #6 #7 #8 (best practice) #9 (second best practice) ENCRYPTION_SEEDS Set Set Set Not set Set Set Not set Not set Set LM_SEEDS Not set Set Not set Set Not Set Set Set Set Set TRL_KEYS / CRO_KEYS (Pre 8.1) Not set Not set Not set Not set Set Set Set Set Set LM_STRENGTH LICENSE_KEY LICENSE_KEY DEFAULT DEFAULT 113/163/239BIT 113/163/239BIT 113/163/239BIT 113/163/239BIT 113/163/239BIT Signature keyword None None SIGN SIGN SIGN SIGN andSIGN2 SIGN SIGN SIGN andSIGN2 Signature type Bespoke symmetric   Bespoke symmetric Bespoke symmetric Bespoke symmetric TRL1 SIGN: TRL1 SIGN2: TRL2 TRL2 TRL2 SIGN: TRL1 SIGN2: TRL2 Signature length (chars) 12 or 20 12 or 20 12 12 60/84/120 2 x 60/84/120 60/84/120 60/84/120 2 x 60/84/120 Client version Pre-8.1 8.1+ 7.1 - 8.1 8.1+ 7.1 - 8.1 8.1+ 8.1+ 10.8.6+ 10.8.6+ Library linkage lmgr.lib lmgr.lib lmgr.lib lmgr.lib lmgr.lib lmgr.lib lmgr.lib lmgr_trl.lib lmgr_trl.lib Note: TRL1 = ECDSA signature TRL2 = Improved ECDSA signature FNP docs refer to these TRL1 and TRL2 signatures when discussing SIGN2   Configuration 6 clients require licenses with the SIGN2 keyword: changing a served license file from configuration 6 to 7 or 8 would break these existing clients. Therefore, in order to move on from SIGN2, producers needs to retire or upgrade their SIGN2-based production client base. In light of this, Flexera will maintain SIGN2 support until further notice to maintain license-server backward compatibility with 'recent' SIGN2 clients. Please review FNP release notes for notifications of changes to this policy. When producers update their clients, they should prefer configuration 8, which is the most secure and simplest license signature configuration. This will allow (eventual) retiring of SIGN2. If SIGN2 is still required, then at least move to configuration 9. Note: The standard lmgr.lib allows verification of all signature types, whereas the recommended lmgr_trl.lib allows verification only of TRL signatures. There are multiple known cases of a binary patch in a configuration 6 client which cause it to allow verification of a legacy symmetric signature presented as SIGN and/or SIGN2 signatures in a rogue license file. Clients based on configurations 5 and 7 are vulnerable to a similar attack vector. The keys used in the old symmetric signatures are easily brute forced, allowing rogue license files like this to be widely generated. This is why Flexera strongly recommends configuration 8 (or 9), where clients can verify only a TRL signature.
View full article
Question: Is it possible to specify a VM_UUID on a FEATURE/INCREMENT line in a license file? Answer: Unfortunately it is not currently possible to specify a VM_UUID on a FEATURE/INCREMENT line in a license file. This is stated on page 17 of the "Understanding Virtualization Features in FlexNet Publisher" White Paper (see PDF attached): "VM_UUID is not currently supported as a HostID on the INCREMENT line. However, one can call lc_hostid(lm_job, VM_UUID, buf) from the client, which means producers can use VM_UUID indirectly as a VDH (vendor defined hostid).   Alternatively, the ETHER HostID is the most flexible for clients on virtual environments."
View full article
Summary CVE-2018-20034 has been discovered and remediated in FlexNet Publisher Symptoms ****Only the following information is permitted to be distributed outside of Flexera Software and customers of FlexNet Publisher:         - CVE number         - CWE ID         - CVSS scores         - Reference to any publicly-available information **** A Denial of Service vulnerability related to adding an item to a list in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor daemon to stop, and the vendor daemon to shut down. Depending upon the license model(s) you offer to your customers, you may or may not distribute one or both of these components to one or more of your customers. If you don’t distribute either of these components, there is no further action on your part. If you do, you must distribute to those same customers the security update mentioned in the Resolution section of this article. This security vulnerability has been assigned the CVE ID number of CVE-2018-20034. Cause For security reasons, Flexera will not publish the cause of this security vulnerability. Steps To Reproduce For security reasons, Flexera Software will not publish the steps to reproduce this security vulnerability. Resolution The FlexNet Publisher 11.16.2 addresses the security vulnerability and is available from Flexera’s Product and License Center (https://flexerasoftware.flexnetoperations.com/control/inst/login?nextURL=%2Fcontrol%2Finst%2Findex): FlexNet Publisher 2018 R4 We advise all FlexNet Publisher customers update lmgrd to FlexNet Publisher 11.16.2, and the vendor daemon as soon as possible after that. Please note that lmadmin or clients are not affected. As a reminder, Flexera no longer distributes the lmgrd executables to end customers; your end customers can only receive the lmgrd executable from you. Workaround No workaround available. Additional Information Please be aware that network access to the FlexNet Publisher License Server would be necessary to perform any attack. Protecting the license server from unauthorized access is essential to minimize the opportunities for any of the vulnerabilities to be exploited. Customers are also strongly advised to follow best practice in protecting the license server from unauthorized access. Related Documents https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20034 https://nvd.nist.gov/vuln/detail/CVE-2018-20034
View full article
Summary CVE-2018-20033 has been discovered and remediated in FlexNet Publisher Symptoms ****Only the following information is permitted to be distributed outside of Flexera Software and customers of FlexNet Publisher:         - CVE number         - CWE ID         - CVSS scores         - Reference to any publicly-available information **** A Remote Code Execution (RCE) vulnerability exists on all platforms in versions 11.16.1.0 or earlier of the following FlexNet Publisher components: lmgrd executable, provided by Flexera Software vendor daemon executable, built by each FlexNet Publisher customer from object code provided by Flexera Depending upon the license model(s) you offer to your customers, you may or may not distribute one or both of these components to one or more of your customers. If you don’t distribute either of these components, there is no further action on your part. If you do, you must distribute to those same customers the security update mentioned in the Resolution section of this article. This security vulnerability has been assigned the CVE ID number of CVE-2018-20033. The vulnerability could allow a remote attacker to corrupt the memory by allocating / de-allocating memory, loading lmgrd or the vendor daemon, and causing the heartbeat between lmgrd and the vendor daemon to stop. This would force the vendor daemon to shut down. No exploit of this vulnerability has been demonstrated. Cause For security reasons, Flexera will not publish the cause of this security vulnerability. Steps To Reproduce For security reasons, Flexera Software will not publish the steps to reproduce this security vulnerability. Resolution The FlexNet Publisher 11.16.2 addresses the security vulnerability and is available from Flexera’s Product and License Center: FlexNet Publisher 2018 R4 We advise all FlexNet Publisher customers update lmgrd to FlexNet Publisher 11.16.2, and the vendor daemon as soon as possible after that. Please note that lmadmin or clients are not affected. As a reminder, Flexera no longer distributes the lmgrd executables to end customers; your end customers can only receive the lmgrd executable from you. Workaround No workaround available. Additional Information Please be aware that network access to the FlexNet Publisher License Server would be necessary to perform any attack. Protecting the license server from unauthorized access is essential to minimize the opportunities for any of the vulnerabilities to be exploited. Customers are also strongly advised to follow best practice in protecting the license server from unauthorized access. Related Documents https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20033 https://nvd.nist.gov/vuln/detail/CVE-2018-20033
View full article
Summary CVE-2018-20032 has been discovered and remediated in FlexNet Publisher Symptoms ****Only the following information is permitted to be distributed outside of Flexera Software and customers of FlexNet Publisher:         - CVE number         - CWE ID         - CVSS scores         - Reference to any publicly-available information **** A Denial of Service vulnerability related to message decoding in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor daemon to stop, and the vendor daemon to shut down. Depending upon the license model(s) you offer to your customers, you may or may not distribute one or both of these components to one or more of your customers. If you don’t distribute either of these components, there is no further action on your part. If you do, you must distribute to those same customers the security update mentioned in the Resolution section of this article. This security vulnerability has been assigned the CVE ID number of CVE-2018-20032. Cause For security reasons, Flexera will not publish the cause of this security vulnerability. Steps To Reproduce For security reasons, Flexera Software will not publish the steps to reproduce this security vulnerability. Resolution The FlexNet Publisher 11.16.2 addresses the security vulnerability and is available from Flexera’s Product and License Center: FlexNet Publisher 2018 R4 We advise all FlexNet Publisher customers update lmgrd to FlexNet Publisher 11.16.2, and the vendor daemon as soon as possible after that. Please note that lmadmin or clients are not affected. As a reminder, Flexera no longer distributes the lmgrd executables to end customers; your end customers can only receive the lmgrd executable from you. Workaround No workaround available. Additional Information Please be aware that network access to the FlexNet Publisher License Server would be necessary to perform any attack. Protecting the license server from unauthorized access is essential to minimize the opportunities for any of the vulnerabilities to be exploited. Customers are also strongly advised to follow best practice in protecting the license server from unauthorized access. Related Documents https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20032 https://nvd.nist.gov/vuln/detail/CVE-2018-20032
View full article
Summary CVE-2018-20031 has been discovered and remediated in FlexNet Publisher Symptoms ****Only the following information is permitted to be distributed outside of Flexera Software and customers of FlexNet Publisher:         - CVE number         - CWE ID         - CVSS scores         - Reference to any publicly-available information **** A Denial of Service vulnerability related to preemptive item deletion in lmgrd and vendor daemon components of FlexNet Publisher version 11.16.1.0 and earlier allows a remote attacker to send a combination of messages to lmgrd or the vendor daemon, causing the heartbeat between lmgrd and the vendor daemon to stop, and the vendor daemon to shut down. Depending upon the license model(s) you offer to your customers, you may or may not distribute one or both of these components to one or more of your customers. If you don’t distribute either of these components, there is no further action on your part. If you do, you must distribute to those same customers the security update mentioned in the Resolution section of this article. This security vulnerability has been assigned the CVE ID number of CVE-2018-20031. Cause For security reasons, Flexera will not publish the cause of this security vulnerability. Steps To Reproduce For security reasons, Flexera Software will not publish the steps to reproduce this security vulnerability. Resolution The FlexNet Publisher 11.16.2 addresses the security vulnerability and is available from Flexera’s Product and License Center: FlexNet Publisher 2018 R4 We advise all FlexNet Publisher customers update lmgrd to FlexNet Publisher 11.16.2, and the vendor daemon as soon as possible after that. Please note that lmadmin or clients are not affected. As a reminder, Flexera no longer distributes the lmgrd executables to end customers; your end customers can only receive the lmgrd executable from you. Workaround No workaround available. Additional Information Please be aware that network access to the FlexNet Publisher License Server would be necessary to perform any attack. Protecting the license server from unauthorized access is essential to minimize the opportunities for any of the vulnerabilities to be exploited. Customers are also strongly advised to follow best practice in protecting the license server from unauthorized access. Related Documents https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20031 https://nvd.nist.gov/vuln/detail/CVE-2018-20031#vulnCurrentDescriptionTitle
View full article