CVE-2019-10011
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 · uneditedICS/StaticPages/AddTestUsers.aspx in Jenzabar JICS (aka Internet Campus Solution) before 2019-02-06 allows remote attackers to create an arbitrary number of accounts with a password of 1234.
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 confidenceJenzabar JICS before 2019-02-06 has an insecure direct object reference or missing authentication vulnerability in the ICS/StaticPages/AddTestUsers.aspx endpoint. This page, intended for administrators to create test users, does not properly validate authorization, allowing any remote unauthenticated attacker to create arbitrary user accounts with the default password 1234, effectively granting them full system access.
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< 2019-02-06CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Jenzabar JICS installationLocate the Jenzabar Internet Campus Solution installation on the server and determine the installed version number or build date. Check product documentation, installation directories, or admin interfaces for version information.Affected if The installed version is dated before 2019-02-06 or the version number falls below the patched release.
-
Verify vulnerable endpoint existsCheck the web server document root for the presence of the file ICS/StaticPages/AddTestUsers.aspx. If the application is accessible externally, attempt a HEAD or GET request to this URL path to confirm it responds.Affected if The AddTestUsers.aspx file exists and returns an HTTP response, indicating the endpoint is present in the deployment.
-
Confirm endpoint is network accessibleReview firewall rules, network ACLs, or web server configuration to determine whether the /ICS/StaticPages/AddTestUsers.aspx endpoint is reachable from untrusted networks or the public internet.Affected if The endpoint is accessible from outside the trusted administrative network without authentication requirements.
-
Audit application user accountsQuery the Jenzabar JICS user database or admin console to list all user accounts. Look for any accounts that were not created through normal administrative procedures, especially accounts with elevated privileges.Affected if Unexpected user accounts exist in the system, particularly accounts with administrative roles that were not intentionally created by authorized administrators.
A system is affected if it runs Jenzabar JICS dated before 2019-02-06 AND the AddTestUsers.aspx endpoint is present and network-accessible, regardless of whether unauthorized accounts are already present.
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 · scoped2019-02-06
Apply the vendor patch released on or before 2019-02-06 to upgrade Jenzabar JICS to a patched version. As a compensating control, restrict network access to the /ICS/StaticPages/AddTestUsers.aspx endpoint to only trusted administrative IPs until patching is complete.
Any Jenzabar JICS version released after 2019-02-06
- 1. Identify the current Jenzabar JICS (Internet Campus Solution) version installed in your environment
- 2. Contact Jenzabar official support or documentation to obtain the version released after 2019-02-06
- 3. Request and apply the patch/update that addresses the hardcoded credential vulnerability (CVE-2019-10011)
- 4. After upgrading, verify that the ICS/StaticPages/AddTestUsers.aspx page is either removed, disabled, or properly secured
- 5. Change any default passwords that may have been used and implement proper access controls
- 6. Audit existing user accounts created through this vulnerability and remove any unauthorized accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10011 — 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-2019-10011 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