CVE-2024-55515: A vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 3.90.
Noroxi assessment
Priority: Monitor (action score 39/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.59% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
A vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 3.90. The component affected by this issue is /upload_ipslib.php on the web interface. By crafting a suitable form name, arbitrary files can be uploaded.
- Published
- Dec 17, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 49th percentile
- CWE
- CWE-22
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
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.
| Vendor | Product | CPE |
|---|---|---|
| raisecom | msg2300 firmware | cpe:2.3:o:raisecom:msg2300_firmware |
| raisecom | msg2300 | cpe:2.3:h:raisecom:msg2300 |
| raisecom | msg2100e firmware | cpe:2.3:o:raisecom:msg2100e_firmware |
| raisecom | msg2100e | cpe:2.3:h:raisecom:msg2100e |
| raisecom | msg2200 firmware | cpe:2.3:o:raisecom:msg2200_firmware |
| raisecom | msg2200 | cpe:2.3:h:raisecom:msg2200 |
| raisecom | msg1200 firmware | cpe:2.3:o:raisecom:msg1200_firmware |
| raisecom | msg1200 | cpe:2.3:h:raisecom:msg1200 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- raisecom msg1200 firmware3.90
- raisecom msg2100e firmware3.90
- raisecom msg2200 firmware3.90
- raisecom msg2300 firmware3.90
Same product
raisecom: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-7120Raisecom MSG1200/MSG2100E/MSG2200/MSG2300 Web Interface list_base_config.php os command injection49Plan
- CVE-2024-55516A vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 v3.90.36Monitor
- CVE-2024-55513A vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 3.90.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-7469Aug 5, 2024 · Raisecom MSG1200/MSG2100E/MSG2200/MSG2300 Web Interface list_vpn_web_custom.php sslvpn_config_mod os command injection28Monitor
- ← EarlierCVE-2024-7470Aug 5, 2024 · Raisecom MSG1200/MSG2100E/MSG2200/MSG2300 Web Interface vpn_template_style.php sslvpn_config_mod os command injection28Monitor
- ← EarlierCVE-2024-55514Dec 17, 2024 · A vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 3.90.25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-555130 days apartA vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 3.90.36Monitor
- CVE-2024-555160 days apartA vulnerability was found in Raisecom MSG1200, MSG2100E, MSG2200, and MSG2300 v3.90.36Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.