CVE-2023-4767
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 · uneditedA CRLF injection vulnerability has been found in ManageEngine Desktop Central affecting version 9.1.0. This vulnerability could allow a remote attacker to inject arbitrary HTTP headers and perform HTTP response splitting attacks via the fileName parameter in /STATE_ID/1613157927228/InvSWMetering.csv.
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 confidenceA CRLF injection vulnerability in ManageEngine Desktop Central v9.1.0 allows remote attackers to inject arbitrary HTTP headers via the fileName parameter in the /STATE_ID/1613157927228/InvSWMetering.csv endpoint. By inserting CRLF sequences, attackers can perform HTTP response splitting attacks.
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= 9.1.0CVSS 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.
-
Confirm ManageEngine Desktop Central is installedCheck for Desktop Central services or web applications running on the system. Common ports include 8383, 8020, or 8080. Look for the Desktop Central service in Windows Services or process list.Affected if Desktop Central is not installed on the system
-
Verify the installed version is 9.1.0Access the Desktop Central web interface and locate the version information, typically found in the About section or at the bottom of the login page. Alternatively, check installation logs or registry entries for the exact version number.Affected if The installed version is exactly 9.1.0
-
Confirm the InvSWMetering.csv endpoint is accessibleAttempt to access the /STATE_ID/*/InvSWMetering.csv path on the Desktop Central server. This endpoint is typically available under the software metering or inventory features accessible to authenticated users.Affected if The endpoint returns a valid response and accepts the fileName parameter
-
Test for CRLF injection in the fileName parameterSend a crafted HTTP request to the vulnerable endpoint with CRLF sequences in the fileName parameter (URL-encoded as %0D%0A). For example: /STATE_ID/1613157927228/InvSWMetering.csv?fileName=test%0D%0ACustom-Header:value. Examine the response for evidence of header injection.Affected if The response contains the injected custom header or shows split HTTP responses, indicating successful CRLF injection
A system is affected if it runs ManageEngine Desktop Central version 9.1.0 with the /InvSWMetering.csv endpoint accessible and the fileName parameter vulnerable to CRLF injection.
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 vendor patches for ManageEngine Desktop Central v9.1.0; alternatively, implement input validation to strip or reject CRLF sequences (\r\n) from the fileName parameter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4767 — 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-2023-4767 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