CVE-2019-6319
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 · uneditedHP DeskJet 3630 All-in-One Printers models F5S43A - F5S57A, K4T93A - K4T99C, K4U00B - K4U03B, and V3F21A - V3F22A (firmware version SWP1FN1912BR or higher) have a Cross-Site Request Forgery (CSRF) vulnerability that could lead to a denial of service (DOS) or device misconfiguration.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in HP DeskJet 3630 All-in-One Printer web interface (firmware SWP1FN1912BR+) allows attackers to trick authenticated users into performing unintended actions, potentially causing denial of service or device misconfiguration.
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< swp1fn1912br< swp1fn1912br< swp1fn1912br< swp1fn1912br< swp1fn1912br< swp1fn1912br< swp1fn1912br< swp1fn1912brCVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 the printer modelAccess the printer's embedded web server by entering its IP address in a web browser. Look for the device information or status page that displays the model name (e.g., HP DeskJet 3630 series).Affected if The device is not an HP DeskJet 3630 series printer.
-
Locate the firmware versionIn the printer's web interface, navigate to the General or About/Information section. Look for a firmware version string such as SWP1FN1912BR or earlier (e.g., SWP1FN1912AS, SWP1FN1912BN).Affected if No firmware version is displayed or the web interface is inaccessible.
-
Verify the web interface is accessibleConfirm the printer's IP address is reachable on the network and the HTTP/HTTPS web server responds. Try accessing http://<printer-ip> in a browser.Affected if The web interface is not reachable or requires no authentication.
-
Compare firmware version against the affected rangeCheck if the installed firmware version is older than swp1fn1912br. The affected versions include: F5s43a, F5s57a, K4t93a, K4t99c, K4u00b, K4u03b, V3f21a, V3f22a with firmware versions below swp1fn1912br.Affected if The installed firmware version is swp1fn1912br or newer.
You are affected if the device is an HP DeskJet 3630 series with a firmware version earlier than swp1fn1912br and its web interface is network-accessible.
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 dataApply available firmware updates if released; otherwise implement network segmentation to restrict web interface access and deploy compensating controls such as Origin/Referer header validation at the network layer.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6319 — 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-6319 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