CVE-2024-12867
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 · uneditedServer-Side Request Forgery in URL Mapper in Arctic Security's Arctic Hub versions 3.0.1764-5.6.1877 allows an unauthenticated remote attacker to exfiltrate and modify configurations and data.
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 confidenceServer-Side Request Forgery (SSRF) vulnerability in the URL Mapper component of Arctic Hub allows unauthenticated remote attackers to make the server perform arbitrary requests to internal or external resources, enabling exfiltration and modification of configurations and sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Authentication
- None
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:H/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:M/U:Amber
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 Arctic Hub is installedLocate the Arctic Hub installation directory or check for running processes named 'arctic-hub' or similar. Common locations include /opt/arctic-hub, C:\Program Files\Arctic Hub, or via system inventory tools.Affected if Arctic Hub software is found on the system
-
Determine the installed Arctic Hub versionCheck the version of Arctic Hub using the vendor-provided method: look for a version file in the installation directory, run 'arctic-hub --version' if available, or examine the application properties/metadata.Affected if The installed version falls within 3.0.1764 to 5.6.1877 inclusive
-
Verify if URL Mapper component is enabledExamine the Arctic Hub configuration files (typically found in config/ or conf/ directories) for settings related to 'urlmapper', 'url-mapper', or 'URL Mapper' and check if the component is set to enabled or active.Affected if The URL Mapper component is enabled or present in the configuration
-
Check for URL input handling in URL MapperReview the URL Mapper configuration or application logs to see if URL parameters are accepted as user input. Look for endpoint configurations that accept URL values.Affected if The URL Mapper accepts URL parameters from users or external sources
-
Assess network exposure of the URL MapperDetermine if the URL Mapper interface is accessible to unauthenticated users. Check firewall rules, authentication settings, and whether the component is exposed to the network or only to authenticated administrators.Affected if The URL Mapper is accessible without authentication or lacks proper access controls
The system is affected if Arctic Hub versions 3.0.1764 through 5.6.1877 are installed with the URL Mapper component enabled and exposed to user-supplied URL input without authentication restrictions.
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 vendor patches for Arctic Hub versions 3.0.1764-5.6.1877. If no patch is immediately available, restrict outbound network access from the application server and implement strict input validation on URL parameters in the URL Mapper.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12867 — 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-2024-12867 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