CVE-2000-0449
published 2000-05-01CVE-2000-0449: Omnis Studio 2.4 uses weak encryption (trivial encoding) for encrypting database fields.
PriorityP429critical10CVSS 2.0
AVNACLAuNCCICAC
EXPLOIT
EPSS
2.15%
79.8th percentile
Omnis Studio 2.4 uses weak encryption (trivial encoding) for encrypting database fields.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| omnis | studio | — | — |
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No detection rules found.
Exploit-DB
CA BrightStor ARCserve - 'msgeng.exe' Remote Heap Overflow (1)
exploitdb·2007-01-27
CVE-2007-0449 CA BrightStor ARCserve - 'msgeng.exe' Remote Heap Overflow (1)
CA BrightStor ARCserve - 'msgeng.exe' Remote Heap Overflow (1)
---
#!/usr/bin/python
# I couldnt find a reliable exploit for my analysis and so came up with this.
# Remote exploit for the CA BrightStor msgeng.exe service heap overflow
# vulnerability as described in LS-20060313.pdf on lssec.com. The exploit was
# tested on windows 2000 SP0. Opens a shell on TCP port 4444. Shouldnt be hard
# to port to other platforms. The exploit overwrites the
# UnhandledExceptionFilter in windows 2000 SP0 (located at 77EE044C) with the
# address of call dword ptr [esi +4C] located in user32.dll. At the time when
# UEF is called esi +4C contains a pointer to our shellcode.
#
# Winny M Thomas ;-)
# Author shall bear no responsibility for any screw ups caused by using this code
from impacket.dcerpc impor
Exploit-DB
Omnis Studio 2.4 - Weak Database Field Encryption
exploitdb·2000-05-25
CVE-2000-0449 Omnis Studio 2.4 - Weak Database Field Encryption
Omnis Studio 2.4 - Weak Database Field Encryption
---
source: https://www.securityfocus.com/bid/1255/info
Omnis Studio 2.4 is a development tool for creating database applications. The tool gives developers the option to encrypt database entries. However, the encryption scheme used is weak and easily broken with any scientific calculator (or even pen and paper, if the attacker has a good knowlege of hex and ASCII). Each unencrypted byte is simply replaced with a value that depends on that byte's original value and the remainder of its position in the string divided by 4.
Note that this vulnerability does not affect the security of Omnis Studio directly, but will be present in all applications that were designed using Omnis Studio.
e=encrypted byte
p=byte's position in the string, mod
No writeups or analysis indexed.
2000-05-01
Published