CVE-2022-42343
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 · uneditedAdobe Campaign version 7.3.1 (and earlier) and 8.3.9 (and earlier) are affected by a Server-Side Request Forgery (SSRF) vulnerability that could lead to arbitrary file system read. A low-privilege authenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.
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 confidenceAdobe Campaign versions 7.3.1 and earlier and 8.3.9 and earlier contain a Server-Side Request Forgery (SSRF) vulnerability allowing low-privilege authenticated attackers to inject arbitrary URLs, forcing the application to make requests to attacker-controlled endpoints. This can be leveraged to read arbitrary files from the filesystem via file:// URLs or internal service access.
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< 7.3.2>= 8.0.0, < 8.4.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Adobe Campaign versionAccess the Adobe Campaign client or admin console and locate the version information (typically in Help > About or via the administration interface). Alternatively, check the installation logs or package metadata.Affected if The installed version is 7.3.1 or earlier, or 8.0.0 through 8.3.9 inclusive, or any version below 8.4.2 for the 8.x branch.
-
Determine if Campaign web or API interfaces are exposedReview network configuration and firewall rules to check if Adobe Campaign web services (port 8080 by default, or 443/80 for IIS/Apache) are accessible from untrusted networks or the internet.Affected if The web or API interface is exposed to the network without strict access controls.
-
Identify URL-handling endpoints in the applicationReview Adobe Campaign workflow configurations, JSSP scripts, and web applications for code that accepts URL parameters and makes outbound HTTP requests (such as HttpClient, SOAP calls, or URLFetch functions).Affected if The application contains custom or out-of-the-box workflows, scripts, or pages that accept user-supplied URLs and process them without strict validation.
-
Audit low-privilege user accounts and permissionsUsing the Adobe Campaign administration console, review user accounts and confirm which ones have operator roles that permit access to workflow execution, JSSP, or web app functionality.Affected if Low-privilege or operator-level accounts exist that can access the URL-handling functionality without additional approval.
-
Check for existing URL allow-listing or input validationInspect Adobe Campaign configuration files (such as serverConf.xml or custom JSSP) for any implemented URL validation patterns, allow-lists, or SSRF protections.Affected if No URL allow-listing or strict input validation is configured for outbound request functionality.
You are affected if your Adobe Campaign installation runs version 7.3.1 or earlier, or any version from 8.0.0 to 8.3.9, and the application exposes web interfaces or APIs that accept URL parameters accessible to low-privilege authenticated users.
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 · scoped7.3.28.4.2
Update Adobe Campaign to versions 7.3.2 and 8.4.0 or later. If immediate patching is not possible, implement URL allow-listing, restrict outbound network access, and disable or validate URL parameter inputs to prevent arbitrary request injection.
Campaign 7.x: upgrade to 7.3.2 or later; Campaign 8.x: upgrade to 8.4.2 or later
- Identify the currently installed Adobe Campaign version (7.x or 8.x branch)
- For Campaign 7.x installations: Upgrade to version 7.3.2 or later
- For Campaign 8.x installations: Upgrade to version 8.4.2 or later
- After upgrade, verify the SSRF vulnerability is resolved by confirming the application no longer allows arbitrary URL injection from low-privilege accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42343 — 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-2022-42343 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