CVE-2023-49105: Security vulnerability
CVE-2023-49105 affects the affected technology. An attacker can access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured.
What happened
The vulnerability, tracked as CVE-2023-49105 (CVSS score: 9 8), is a case of. A security weakness in the affected technology is being tracked as CVE-2023-49105. CVE-2023-49105 affects the affected technology.
An attacker can access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured. An issue was discovered in ownCloud owncloud/core before 10. Cybersecurity and Infrastructure Security Agency (CISA) on Thursday added a critical security flaw impacting ownCloud to its Known Exploited Vulnerabilities (KEV) catalog following reports that a Chinese-speaking threat actor weaponized the vulnerability to target a nuclear research body in the Philippines.
ownCloud Flaw Exploited to Steal Nuclear Records From Philippine Research Body. The earliest affected version is 10 6 0. This occurs because pre-signed URLs can be accepted even when no signing-key is configured for the owner of the files.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
An issue was discovered in ownCloud owncloud/core before 10.
This occurs because pre-signed URLs can be accepted even when no signing-key is configured for the owner of the files.
Cybersecurity and Infrastructure Security Agency (CISA) on Thursday added a critical security flaw impacting ownCloud to its Known Exploited Vulnerabilities (KEV) catalog following reports that a Chinese-speaking threat actor weaponized the vulnerability to target a nuclear research body in the Philippines.
ownCloud Flaw Exploited to Steal Nuclear Records From Philippine Research Body
A security weakness in the affected technology is being tracked as CVE-2023-49105. An attacker can access, modify, or delete any file without authentication if the username of a victim is known, and the victim has no signing-key configured. This occurs because pre-signed URLs can be accepted even when no signing-key is configured for the owner of the files. The earliest affected version is 10.6.0. Cybersecurity and Infrastructure Security Agency (CISA) on Thursday added a critical security flaw impacting ownCloud to its Known Exploited Vulnerabilities (KEV) catalog following reports that a Chinese-speaking threat actor weaponized the vulnerability to target a nuclear research body in the Philippines. The vulnerability, tracked as CVE-2023-49105 (CVSS score: 9.8), is a case of.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
the affected technology is present and the vulnerable function or code path is reachable in normal application use.
attacker-controlled input or the relevant workflow reaches the the reported vulnerability condition described in the advisory.
the the reported vulnerability condition is triggered inside the affected technology, creating the security boundary failure described by the advisory.
successful exploitation reaches the confidentiality, integrity or availability impact described in the vendor or vulnerability record.
Why this matters to you
CVE-2023-49105 matters because the practical risk is not the score alone — it is whether the affected technology or service is 10 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service is 10.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for the affected technology or service is 10.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.