CVE-2024-12056: Client Secret not checked with OAuth Password grant type
Noroxi assessment
Priority: Monitor (action score 9/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. Special conditions such as timing or configuration are required.
- Fixed version: arcinfo PcVue 16.2.2.
Low priority for now. Upgrade to arcinfo PcVue 16.2.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The Client secret is not checked when using the OAuth Password grant type. By exploiting this vulnerability, an attacker could connect to a web server using a client application not explicitly authorized as part of the OAuth deployment. Exploitation requires valid credentials and does not permit the attacker to bypass user privileges.
- Published
- Dec 4, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-358
Report tools
Action score
9
Low priority for now.
- CVSS
- 9 / 40 · 2.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · arcinfo
- 2.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/AU:N/R:U/RE:M/U:Green
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (arcinfo). Independent of NVD's CPE analysis and usually ahead of it.
arcinfo PcVue
- 12.0 and later · before 16.2.2affected · cpe
Same product
arcinfo: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-26867ARC Informatique PcVue Deserialization of Untrusted Data40Plan
- CVE-2026-14868Weak encryption mechanism for User directory33Monitor
- CVE-2020-26869ARC Informatique PcVue Exposure of Sensitive Information to an Unauthorized Actor31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-4311Dec 12, 2022 ·
An insertion of sensitive information into log file vulnerability exists in PcVue versions 15 through 15.2.2.26Monitor
- ← EarlierCVE-2022-4312Dec 12, 2022 ·
A cleartext storage of sensitive information vulnerability exists in PcVue versions 8.10 through 15.2.3.22Monitor
- Later →CVE-2024-12057Dec 9, 2024 · User credentials recorded in log files7Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| arcinfo PcVue | 16.2.2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-358 · Improperly Implemented Security Check for StandardCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/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:X/RE:M/U:Green
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.