CVE-2019-9542
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 · unedited: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in itemlookup.asp of Telos Automated Message Handling System allows a remote attacker to inject arbitrary script into an AMHS session. This issue affects: Telos Automated Message Handling System versions prior to 4.1.5.5.
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 confidenceCross-site scripting (XSS) vulnerability in the itemlookup.asp page of Telos Automated Message Handling System (AMHS) allows remote attackers to inject arbitrary JavaScript into AMHS user sessions. The lack of proper input sanitization on this page permits stored XSS where malicious scripts execute when other users access the compromised content.
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< 4.1.5.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Identify Telos AMHS installationLocate the Telos AMHS installation directory or service on the system. Common locations include C:\Program Files\Telos\AMHS or the web root directory serving the application.Affected if Telos AMHS is installed and the itemlookup.asp page is accessible over HTTP/HTTPS.
-
Determine installed versionCheck the version of Telos AMHS by examining the application executable, DLL properties, or version information in the installation directory. Look for version.txt, a README file, or right-click the main executable to view properties.Affected if The installed version is lower than 4.1.5.5 (e.g., 4.1.4.x, 4.1.3.x, etc.).
-
Locate itemlookup.asp pageSearch for the itemlookup.asp file within the web application directory structure. This file should exist in the web-accessible portion of the AMHS application.Affected if The file itemlookup.asp exists and is served by the web server.
-
Verify XSS input fields existExamine the itemlookup.asp page source code or functionality to identify user input fields (query parameters, form inputs) that accept and display user-supplied data without sanitization.Affected if The page accepts user input and reflects it back in the response without proper encoding or validation.
The environment is affected if Telos AMHS version is lower than 4.1.5.5 and the itemlookup.asp page is accessible and processes user input 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 data4.1.5.5
Upgrade to Telos AMHS version 4.1.5.5 or later. If immediate patching is not possible, implement input validation and output encoding on the itemlookup.asp page, and consider deploying a WAF rule to block XSS payloads targeting this endpoint.
- 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-9542 — 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-9542 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