CVE-2023-43800
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 · uneditedArduino Create Agent is a package to help manage Arduino development. The vulnerability affects the endpoint `/v2/pkgs/tools/installed`. A user who has the ability to perform HTTP requests to the localhost interface, or is able to bypass the CORS configuration, can escalate his privileges to those of the user running the Arduino Create Agent service via a crafted HTTP POST request. This issue has been addressed in version `1.3.3`. Users are advised to upgrade. There are no known workarounds for this issue.
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 confidenceArduino Create Agent contains a privilege escalation vulnerability in the `/v2/pkgs/tools/installed` endpoint. An attacker with localhost HTTP access or CORS bypass capability can send a crafted HTTP POST request to escalate their privileges to match the user account running the Arduino Create Agent service.
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< 1.3.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if Arduino Create Agent is installedCheck for the Arduino Create Agent service or executable. On Windows: look in Program Files for 'ArduinoCreateAgent' folder, check Services list for 'Arduino Create Agent'. On Linux/Mac: check /usr/local/ArduinoCreateAgent or ~/ArduinoCreateAgent directories, or run 'ps aux | grep -i arduino' to find running processes.Affected if The software is not present on the system, then not affected.
-
Determine the installed versionCheck the version of the Arduino Create Agent executable or service. On Windows: right-click the executable in Program Files > Properties > Details tab. On Linux/Mac: run the agent with --version flag or check the version file in the installation directory.Affected if Version is less than 1.3.3 (e.g., 1.3.2, 1.3.1, 1.3.0, or earlier versions).
-
Verify service user contextCheck what user account the Arduino Create Agent service runs as. On Windows: open Services > right-click 'Arduino Create Agent' > Properties > Log On tab. On Linux: run 'ps aux | grep arduino' to see the process owner.Affected if The service runs as an administrator, root, or a privileged user account that would grant the attacker elevated access upon exploitation.
-
Check network exposure of the vulnerable endpointDetermine if the Arduino Create Agent API is accessible over network or only on localhost. Check firewall rules and the agent's configuration for binding address. The agent typically listens on localhost:8991 or similar port.Affected if The agent API port (usually 8991) is exposed to network interfaces other than localhost, or CORS headers allow cross-origin requests from untrusted sources.
A user is affected if Arduino Create Agent version is below 1.3.3, the service runs with elevated privileges, and the /v2/pkgs/tools/installed API endpoint is accessible via localhost or network with CORS bypass potential.
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 · scoped1.3.3
Upgrade Arduino Create Agent to version 1.3.3 or later. There are no available workarounds.
1.3.3
- Upgrade Arduino Create Agent to version 1.3.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43800 — 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-43800 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