CVE-2021-37498
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 · uneditedAn SSRF issue was discovered in Reprise License Manager (RLM) web interface through 14.2BL4 that allows remote attackers to trigger outbound requests to intranet servers, conduct port scans via the actserver parameter in License Activation function.
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 confidenceAn SSRF vulnerability in Reprise License Manager (RLM) web interface (versions up to 14.2BL4) allows remote attackers to abuse the actserver parameter in the License Activation function to make the server perform arbitrary outbound requests to internal/intranet resources and conduct port scanning of internal networks.
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< 17.0CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Confirm RLM web interface is exposedCheck if the RLM web server is running and accessible on the network. Default RLM web ports are 5054 and 8080. Use a browser or curl to access http://your-rlm-host:5054/ or check with 'netstat -an | grep -E "5054|8080"' to see if these ports are listening.Affected if The RLM web interface is reachable from an untrusted network (e.g., the internet or less-trusted internal segments).
-
Identify installed RLM versionCheck the RLM version by examining the rlm executable or the web interface banner. On Linux, run 'rlm -v' or check the binary file version. The web interface typically displays version info on the login page or in server status pages.Affected if The installed version is any release prior to version 17.0 (including all versions up to and including 14.2BL4).
-
Locate License Activation functionAccess the License Activation page in the RLM web interface. The vulnerable endpoint is typically found under the 'Activation' or 'License Management' section of the web admin panel. Look for forms or API endpoints that accept an 'actserver' parameter.Affected if The License Activation feature is enabled and accessible through the web interface.
-
Verify actserver parameter handlingInspect the RLM configuration files (rlm.conf and any vendor configuration files) to see if there is input validation or allowlisting configured for the actserver parameter used in activation requests. Check if the web server logs show attempts to use internal IP addresses (like 127.0.0.1, 10.x.x.x, 192.168.x.x) in the actserver parameter.Affected if There is no strict allowlist validation on the actserver parameter, or outbound network access from the RLM server is not restricted by firewall rules.
Your environment is affected if RLM version is below 17.0 AND the web interface is accessible with the License Activation feature exposed and no allowlist validation exists on the actserver parameter.
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.
dbcve · scoped17.0
Update to a patched version if available, or implement strict allowlist validation for the actserver parameter and restrict outbound network access from the RLM server via firewall rules.
17.0
- 1. Backup the current Reprise License Manager configuration and license files
- 2. Download Reprise License Manager version 17.0 or later from the official vendor website
- 3. Stop the RLM service before upgrading
- 4. Install the version 17.0 update following vendor installation instructions
- 5. Restore the backed-up configuration and license files
- 6. Start the RLM service and verify it is running correctly
- 7. Test the License Activation function to confirm the SSRF vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37498 — 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-2021-37498 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