CVE-2013-2803
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 · uneditedProSoft RadioLinx ControlScape before 6.00.040 uses a deficient PRNG algorithm and seeding strategy for passphrases, which makes it easier for remote attackers to obtain access via a brute-force attack.
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 confidenceProSoft RadioLinx ControlScape before version 6.00.040 uses a flawed PRNG algorithm with inadequate seeding for generating passphrases, enabling attackers to brute-force authentication credentials.
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<= 6.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm RadioLinx ControlScape installationLook for ProSoft RadioLinx ControlScape software on the system, typically found in Program Files or the application's installation directory.Affected if The software is installed on the system
-
Locate the installed versionOpen the application or check the program files directory for version information. The version is typically displayed in the application header or available through the About/Help menu.Affected if Version information cannot be located or shows a version <= 6.00
-
Compare version against the fixed releaseIdentify the full version number (e.g., 6.00.038, 6.00.040, etc.) and compare it to the threshold 6.00.040.Affected if The installed version is 6.00.040 or earlier (e.g., 6.00, 6.00.010, 6.00.038)
-
Check if passphrase generation feature is in useDetermine whether the RadioLinx ControlScape authentication or passphrase generation feature is enabled or configured on the system.Affected if Passphrase-based authentication is configured and the version is <= 6.00.040
If ProSoft RadioLinx ControlScape version 6.00.040 or earlier is installed and passphrase authentication is in use, the environment is vulnerable to CVE-2013-2803.
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 · scopedUpgrade RadioLinx ControlScape to version 6.00.040 or later, which implements a cryptographically secure PRNG with proper seeding for passphrase generation.
6.00.040
- Identify the current version of RadioLinx ControlScape installed in the environment
- Back up all current configurations, user data, and passphrase settings
- Download ProSoft RadioLinx ControlScape version 6.00.040 or later from the official vendor (ProSoft) or ICS-CERT referenced sources
- Stop any active sessions or services using the ControlScape application
- Install the upgrade following the vendor's standard upgrade procedure
- After upgrading, verify the new version is 6.00.040 or higher
- As a security precaution, regenerate all passphrases used in the system after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2803 — 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-2013-2803 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