CVE-2019-5990
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 · uneditedAccess analysis CGI An-Analyzer released in 2019 June 24 and earlier allow remote attackers to obtain a login password via HTTP referer.
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 · moderate confidenceAn-Analyzer is an access analysis CGI script. The vulnerability allows remote unauthenticated attackers to obtain the login password through the HTTP Referer header, indicating improper handling of the referer field that leads to password disclosure.
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-06-24CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Locate the An-Analyzer CGI scriptSearch the web server's cgi-bin or cgi directories for files named 'analyzer', 'an-analyzer', or similar. Common paths include /cgi-bin/, /cgi/, or custom script directories.Affected if The CGI script file exists on the server and is web-accessible
-
Determine the script version or file dateCheck the CGI script file's modification timestamp or inspect the script source code for version strings or copyright dates. Compare against the June 24, 2019 threshold.Affected if The script version or file date is on or before June 24, 2019
-
Verify CGI is processing Referer headersExamine the CGI script source code to confirm it reads or processes the HTTP Referer header. Look for environment variables like HTTP_REFERER or similar referer-related code handling.Affected if The script contains code that processes the Referer header without sanitization
-
Check for exposed password configurationReview the CGI script and any associated configuration files for login password settings. Search for variables named 'password', 'pass', or similar authentication credentials.Affected if Password credentials are stored in plain text within the CGI or config files accessible via the web-facing script
-
Inspect web server logs for Referer-based password leakageReview web server access logs for entries where the Referer header contains what appears to be password data or authentication tokens being logged.Affected if Log entries show password or sensitive data being captured from Referer headers
You are affected if An-Analyzer CGI is installed and accessible, version is on or before June 24, 2019, and the script processes Referer headers without sanitization.
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.
From vendor dataUpgrade to the patched version released after June 24, 2019, or implement web server-level controls to sanitize Referer headers before they reach the CGI application.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5990 — 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-5990 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